1 |
On 07/04/2018 11:43 PM, Kristian Fiskerstrand wrote: |
2 |
> On 07/04/2018 11:28 PM, Michał Górny wrote: |
3 |
>> W dniu śro, 04.07.2018 o godzinie 23∶12 +0200, użytkownik Ulrich Mueller |
4 |
>> napisał: |
5 |
>>>>>>>> On Wed, 04 Jul 2018, Michał Górny wrote: |
6 |
>>>> b. Signing subkey: 1 year maximum |
7 |
>>>> 5. Key expiration date renewed at least 2 weeks before the previous |
8 |
>>>> expiration date. |
9 |
>>> |
10 |
>>> This is crappy as a scheme, since it will make it impossible to keep |
11 |
>>> the expiration date at a constant month and date. |
12 |
>>> |
13 |
>> |
14 |
>> Nobody forces you to prolong it for exactly the same amount, exactly two |
15 |
>> weeks before expiration. The only point made here is to give services |
16 |
>> time to sync rather than the common combo of renewing key once it |
17 |
>> already expired. |
18 |
>> |
19 |
>> Especially, if you follow the recommended scheme below you can easily |
20 |
>> get periodic expiration dates. |
21 |
>> |
22 |
> |
23 |
> As I understand ulm's concern, the issue is with the max 1 year in |
24 |
> combination with this, e.g it effectively prohibits extended a subkey |
25 |
> expiring 2018-12-31 to 2019-12-31 two weeks before, since that exceeds |
26 |
> one year maximum |
27 |
> |
28 |
|
29 |
fwiw, this can be mitigated by allowing e.g 1.25 years / 15 months |
30 |
instead of one year. |
31 |
|
32 |
-- |
33 |
Kristian Fiskerstrand |
34 |
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net |
35 |
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |