| 1 |
On 04-03-2014 09:59:10 -0600, Matthew Summers wrote: |
| 2 |
> On Tue, Mar 4, 2014 at 9:02 AM, Rich Freeman <rich0@g.o> wrote: |
| 3 |
> > Certainly an exhaustive set of instructions on using gpg is too much, |
| 4 |
> > but can we at least get: |
| 5 |
> > 1. A list of steps that can be followed to generate a key that is |
| 6 |
> > useful and compliant with the policy. |
| 7 |
> > 2. A command that can be supplied with a key ID and tell you if the |
| 8 |
> > key complies or not. |
| 9 |
> |
| 10 |
> Please add some instructions/best practice policy on replacing an |
| 11 |
> existing key too :-) |
| 12 |
|
| 13 |
Key expiration (extending the lifetime) is one of the things I find very |
| 14 |
useful and often avoids replacing keys, so I think that should be in it |
| 15 |
too. |
| 16 |
|
| 17 |
|
| 18 |
-- |
| 19 |
Fabian Groffen |
| 20 |
Gentoo on a different level |
Archives