Gentoo Archives: gentoo-dev

From: Markos Chandras <hwoarang@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] please sign your manifests
Date: Wed, 13 Feb 2013 15:48:24
Message-Id: CAG2jQ8jvcEw7Lm9oWMb2r5=YanrVUHA2wx1kbVjA-jYy7kiMQQ@mail.gmail.com
In Reply to: Re: [gentoo-dev] Re: [gentoo-dev-announce] please sign your manifests by "Aaron W. Swenson"
1 On 13 February 2013 15:31, Aaron W. Swenson <titanofold@g.o> wrote:
2 > On Wed, Feb 13, 2013 at 01:20:39PM +0100, Michael Weber wrote:
3 >> On 02/13/2013 11:55 AM, Markos Chandras wrote:
4 >> > http://www.gentoo.org/doc/en/gnupg-user.xml
5 >> >
6 >> still no hint what to do on expiration (as every single other "gpg howto").
7 >>
8 >
9 > It depends. What do you want to do when it expires?
10 >
11 > If you don't believe that the key has been compromised -- nobody is
12 > going around using your key falsely -- then you should just "renew"
13 > your key, i.e change the expiry date.
14 >
15 > Some that are a bit more paranoid will generate a new key, sign it
16 > with the about-to-expire key -- not the already expired key because
17 > they would never allow that to happen -- revoke the about-to-expire
18 > key, then sync with the key server(s).
19 >
20 > This information, by the way, has been blogged about thousands of
21 > times.
22 >
23 > --
24 > Mr. Aaron W. Swenson
25 > Gentoo Linux Developer
26 > Email : titanofold@g.o
27 > GnuPG FP : 2C00 7719 4F85 FB07 A49C 0E31 5713 AA03 D1BB FDA0
28 > GnuPG ID : D1BBFDA0
29
30 Correct. I don't think we need a "Gentoo-specific" document for that.
31
32 --
33 Regards,
34 Markos Chandras - Gentoo Linux Developer
35 http://dev.gentoo.org/~hwoarang