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 v5 03/16] glep-0063: 'Gentoo subkey' → 'Signing subkey'
Date: Wed, 25 Jul 2018 05:39:01
Message-Id: 1532497127.891.2.camel@gentoo.org
In Reply to: Re: [gentoo-dev] [PATCH v5 03/16] glep-0063: 'Gentoo subkey' → 'Signing subkey' by Joshua Kinard
1 W dniu śro, 25.07.2018 o godzinie 01∶28 -0400, użytkownik Joshua Kinard
2 napisał:
3 > On 7/8/2018 2:38 PM, Michał Górny wrote:
4 > > Replace the 'Gentoo subkey' term that might wrongly suggest that
5 > > the developers are expected to create an additional, dedicated subkey
6 > > for Gentoo.
7 > >
8 > > Suggested-by: Kristian Fiskerstrand <k_f@g.o>
9 > > ---
10 > > glep-0063.rst | 2 +-
11 > > 1 file changed, 1 insertion(+), 1 deletion(-)
12 > >
13 > > diff --git a/glep-0063.rst b/glep-0063.rst
14 > > index 0773e3b..f02537d 100644
15 > > --- a/glep-0063.rst
16 > > +++ b/glep-0063.rst
17 > > @@ -116,7 +116,7 @@ Recommendations
18 > >
19 > > a. Root key: 3 years maximum, expiry date renewed annually.
20 > >
21 > > - b. Gentoo subkey: 1 year maximum, expiry date renewed every 6 months.
22 > > + b. Signing subkey: 1 year maximum, expiry date renewed every 6 months.
23 > >
24 > > 5. Create a revocation certificate & store it hardcopy offsite securely
25 > > (it's about ~300 bytes).
26 > >
27 >
28 > I lost track of this due to other priorities, but picking through some of the
29 > follow-up messages about the lead time on renewals and all, I don't have a
30 > problem with that. But why is the maximum of one year on subkey/signing key
31 > expiration still here?
32
33 Because I've started with small changes, and the thing you're asking
34 about is changed in a followup patch. Please read the final text
35 instead of wrongly assuming something from irrelevant change.
36
37 >
38 > I'm not seeing a lot of additional follow-up on that, but that is still too
39 > short. Two years is perfectly fine in this case. I'd prefer three years
40 > myself, but am willing to compromise for two. I am not doing one year unless
41 > someone drops some really convincing logic on me. And no, scrawling "logic" on
42 > the side of an anvil doesn't count.
43 >
44 > Does anyone know what the other projects require for their keys? Without a
45 > proper explanation of //why// one year needs to be the maximum, looking to what
46 > other projects use seems sensible for guidance.
47 >
48 > I can't seem to find any specific guidance from Debian, but FreeBSD appears to
49 > be fine with three years on their committer keys:
50 >
51 > """
52 > A three year key lifespan is short enough to obsolete keys weakened by
53 > advancing computer power, but long enough to reduce key management problems.
54 > """
55 >
56 > https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/article.html#pgpkeys
57 >
58
59 --
60 Best regards,
61 Michał Górny

Attachments

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

Replies