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