Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: gentoo-dev@l.g.o
Cc: robbat2@g.o
Subject: Re: [gentoo-dev] [PATCH v3 10/12] glep-0063: Make 2-yearly expiration term mandatory
Date: Sat, 07 Jul 2018 05:51:12
Message-Id: 1530942659.900.6.camel@gentoo.org
In Reply to: Re: [gentoo-dev] [PATCH v3 10/12] glep-0063: Make 2-yearly expiration term mandatory by Ulrich Mueller
1 W dniu pią, 06.07.2018 o godzinie 08∶40 +0200, użytkownik Ulrich Mueller
2 napisał:
3 > > > > > > On Fri, 06 Jul 2018, Michał Górny wrote:
4 > > Did you even read the text? It's 'at most 2 years'. If you renew it
5 > > every year, you can achieve the desired effect while keeping far
6 > > ahead of the required schedule.
7 >
8 > So effectively we're down from 5 years to 1 year also for the main
9 > key, as a mandatory requirement? That is not what I have perceived
10 > as the consensus in the discussion so far.
11 >
12 > > I really see no point in added complexity just so that someone could
13 > > bend the standard to the limits.
14 >
15 > It isn't complicated in the current version of GLEP 63 ("5 years
16 > maximum"). Simply keep that wording, or moderately shorten it, to
17 > something like 3 years, or 2.25 years. (Or if you prefer round
18 > numbers, 800 days, or 70000000 seconds.) :-)
19 >
20
21 Went for 900 days. This will be easier to test script-wise
22 (i.e. without having to fight over how many days a year has)
23 and give you a long grace period for early renewal (and for keys created
24 late in the year).
25
26 --
27 Best regards,
28 Michał Górny

Attachments

File name MIME type
signature.asc application/pgp-signature