W dniu śro, 04.07.2018 o godzinie 23∶43 +0200, użytkownik Kristian
Fiskerstrand napisał:
> 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
> 

We could say 'N year(s) + 2 weeks' but it would be kinda silly.  Given
that people are unhappy about one year anyway, let's defer this one for
now.

-- 
Best regards,
Michał Górny

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to