| 1 |
On 7/25/2018 1:38 AM, Michał Górny wrote: |
| 2 |
> W dniu śro, 25.07.2018 o godzinie 01∶28 -0400, użytkownik Joshua Kinard |
| 3 |
> napisał: |
| 4 |
>> On 7/8/2018 2:38 PM, Michał Górny wrote: |
| 5 |
>>> Replace the 'Gentoo subkey' term that might wrongly suggest that |
| 6 |
>>> the developers are expected to create an additional, dedicated subkey |
| 7 |
>>> for Gentoo. |
| 8 |
>>> |
| 9 |
>>> Suggested-by: Kristian Fiskerstrand <k_f@g.o> |
| 10 |
>>> --- |
| 11 |
>>> glep-0063.rst | 2 +- |
| 12 |
>>> 1 file changed, 1 insertion(+), 1 deletion(-) |
| 13 |
>>> |
| 14 |
>>> diff --git a/glep-0063.rst b/glep-0063.rst |
| 15 |
>>> index 0773e3b..f02537d 100644 |
| 16 |
>>> --- a/glep-0063.rst |
| 17 |
>>> +++ b/glep-0063.rst |
| 18 |
>>> @@ -116,7 +116,7 @@ Recommendations |
| 19 |
>>> |
| 20 |
>>> a. Root key: 3 years maximum, expiry date renewed annually. |
| 21 |
>>> |
| 22 |
>>> - b. Gentoo subkey: 1 year maximum, expiry date renewed every 6 months. |
| 23 |
>>> + b. Signing subkey: 1 year maximum, expiry date renewed every 6 months. |
| 24 |
>>> |
| 25 |
>>> 5. Create a revocation certificate & store it hardcopy offsite securely |
| 26 |
>>> (it's about ~300 bytes). |
| 27 |
>>> |
| 28 |
>> |
| 29 |
>> I lost track of this due to other priorities, but picking through some of the |
| 30 |
>> follow-up messages about the lead time on renewals and all, I don't have a |
| 31 |
>> problem with that. But why is the maximum of one year on subkey/signing key |
| 32 |
>> expiration still here? |
| 33 |
> |
| 34 |
> Because I've started with small changes, and the thing you're asking |
| 35 |
> about is changed in a followup patch. Please read the final text |
| 36 |
> instead of wrongly assuming something from irrelevant change. |
| 37 |
|
| 38 |
Yep, you're right. Sorry about that! I am fine with the specified timeframe |
| 39 |
in the current iteration. |
| 40 |
|
| 41 |
|
| 42 |
>> |
| 43 |
>> I'm not seeing a lot of additional follow-up on that, but that is still too |
| 44 |
>> short. Two years is perfectly fine in this case. I'd prefer three years |
| 45 |
>> myself, but am willing to compromise for two. I am not doing one year unless |
| 46 |
>> someone drops some really convincing logic on me. And no, scrawling "logic" on |
| 47 |
>> the side of an anvil doesn't count. |
| 48 |
>> |
| 49 |
>> Does anyone know what the other projects require for their keys? Without a |
| 50 |
>> proper explanation of //why// one year needs to be the maximum, looking to what |
| 51 |
>> other projects use seems sensible for guidance. |
| 52 |
>> |
| 53 |
>> I can't seem to find any specific guidance from Debian, but FreeBSD appears to |
| 54 |
>> be fine with three years on their committer keys: |
| 55 |
>> |
| 56 |
>> """ |
| 57 |
>> A three year key lifespan is short enough to obsolete keys weakened by |
| 58 |
>> advancing computer power, but long enough to reduce key management problems. |
| 59 |
>> """ |
| 60 |
>> |
| 61 |
>> https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/article.html#pgpkeys |
| 62 |
>> |
| 63 |
|
| 64 |
-- |
| 65 |
Joshua Kinard |
| 66 |
Gentoo/MIPS |
| 67 |
kumba@g.o |
| 68 |
rsa6144/5C63F4E3F5C6C943 2015-04-27 |
| 69 |
177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943 |
| 70 |
|
| 71 |
"The past tempts us, the present confuses us, the future frightens us. And our |
| 72 |
lives slip away, moment by moment, lost in that vast, terrible in-between." |
| 73 |
|
| 74 |
--Emperor Turhan, Centauri Republic |
Archives