| 1 |
W dniu śro, 04.07.2018 o godzinie 23∶43 +0200, użytkownik Kristian |
| 2 |
Fiskerstrand napisał: |
| 3 |
> On 07/04/2018 11:28 PM, Michał Górny wrote: |
| 4 |
> > W dniu śro, 04.07.2018 o godzinie 23∶12 +0200, użytkownik Ulrich Mueller |
| 5 |
> > napisał: |
| 6 |
> > > > > > > > On Wed, 04 Jul 2018, Michał Górny wrote: |
| 7 |
> > > > |
| 8 |
> > > > b. Signing subkey: 1 year maximum |
| 9 |
> > > > 5. Key expiration date renewed at least 2 weeks before the previous |
| 10 |
> > > > expiration date. |
| 11 |
> > > |
| 12 |
> > > This is crappy as a scheme, since it will make it impossible to keep |
| 13 |
> > > the expiration date at a constant month and date. |
| 14 |
> > > |
| 15 |
> > |
| 16 |
> > Nobody forces you to prolong it for exactly the same amount, exactly two |
| 17 |
> > weeks before expiration. The only point made here is to give services |
| 18 |
> > time to sync rather than the common combo of renewing key once it |
| 19 |
> > already expired. |
| 20 |
> > |
| 21 |
> > Especially, if you follow the recommended scheme below you can easily |
| 22 |
> > get periodic expiration dates. |
| 23 |
> > |
| 24 |
> |
| 25 |
> As I understand ulm's concern, the issue is with the max 1 year in |
| 26 |
> combination with this, e.g it effectively prohibits extended a subkey |
| 27 |
> expiring 2018-12-31 to 2019-12-31 two weeks before, since that exceeds |
| 28 |
> one year maximum |
| 29 |
> |
| 30 |
|
| 31 |
We could say 'N year(s) + 2 weeks' but it would be kinda silly. Given |
| 32 |
that people are unhappy about one year anyway, let's defer this one for |
| 33 |
now. |
| 34 |
|
| 35 |
-- |
| 36 |
Best regards, |
| 37 |
Michał Górny |
Archives