Should gpg always generate a revocation cert?
Mon Sep 22 14:50:02 2003
>From: Neil Williams <firstname.lastname@example.org>
>Organization: www.codehelp.co.uk + www.dclug.org.uk
>To: "GnuPG Users" <email@example.com>
>Subject: Re: Should gpg always generate a revocation cert?
>Date: Sun, 21 Sep 2003 13:26:18 +0100
> perhaps gpg should by default
>> generate a revocation cert when it generates a new key (put
>it in a
>> <keyid>.rev file or so)
>Perhaps just a default YES question in the --gen-key sequence? This
>leaves a potentially crucial file sitting around until the user
>something about it though. Could be a problem when users don't secure
>=2Egnupg/ directory properly.
>I don't know if a default file wouldn't actually make things worse
>- if it =
>put somewhere obvious so that it gets backed up at some point, then
>backup becomes a liability later on. If it's not backed up, there's
>point in generating it - most of these 'lost keys' come about after
>re-install or change of distro / HD corruption.
a possible solution might be to have the default setting be to generate
the revocation certificate as the key is created,
and have the revocation certificate encrypted symmetrically to the same
passphrase as the key,
then prompt for it (and possibly a backup of the key too) to be stored
on a removable disk (floppy, usb, cdrw, etc.)
and to have an over-ride choice (y,n)
at each step, as Adrian suggested
Concerned about your privacy? Follow this link to get
FREE encrypted email: https://www.hushmail.com/?l=2
Free, ultra-private instant messaging with Hush Messenger
Promote security and make money with the Hushmail Affiliate Program: