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