| 1 |
W dniu pią, 06.07.2018 o godzinie 07∶43 +0200, użytkownik Ulrich Mueller |
| 2 |
napisał: |
| 3 |
> > > > > > On Thu, 5 Jul 2018, Michał Górny wrote: |
| 4 |
> > Replace the disjoint 'minimum' and 'recommendation' for expiration |
| 5 |
> > with a single requirement. Make it 2 years. Also, remove disjoint |
| 6 |
> > expiration recommendation for the primary key and subkeys since many |
| 7 |
> > developers fail at implementing that anyway. |
| 8 |
> |
| 9 |
> Still NACK. If expiration is exactly 2 years and renewal must happen |
| 10 |
> 2 weeks before the expiry date, then it is not possible to keep the |
| 11 |
> same date. |
| 12 |
|
| 13 |
Did you even read the text? It's 'at most 2 years'. If you renew it |
| 14 |
every year, you can achieve the desired effect while keeping far ahead |
| 15 |
of the required schedule. |
| 16 |
|
| 17 |
> Example: The key will expire at 2018-12-31, so it must be renewed at |
| 18 |
> 2018-12-17 or earlier. This will make it impossible to keep the same |
| 19 |
> month and day (unless one would reset it to 2019-12-31, which is only |
| 20 |
> one year though). |
| 21 |
> |
| 22 |
> So please, make it something like 2 years + 3 months. |
| 23 |
> |
| 24 |
|
| 25 |
I really see no point in added complexity just so that someone could |
| 26 |
bend the standard to the limits. |
| 27 |
|
| 28 |
-- |
| 29 |
Best regards, |
| 30 |
Michał Górny |
Archives