Should gpg always generate a revocation cert?

[Adrian 'Dagurashibanipal' von Bidder]

--Boundary-02=_ZDYb/aYK+Dj/dBK
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

Yo!

Since there is a 'Lost my key' thread every few weeks: perhaps gpg should b=
y=20
default
 * generate a revocation cert when it generates a new key (put it in a=20
<keyid>.rev file or so)
 * print lengthy explanations about 'the key can not, under no circumstance=
s,=20
be deleted from the keyservers. Really. We mean it. You can ask in the=20
mailing lists, we will tell you this again.'

Of course these features could be disabled by use of the=20
=2D-i-am-no-newbie-thank-you-very-much flag.

(Yes, this is really a feature that should be offered by the user friendly =
GUI=20
keymangaer app that users should use - but I guess the majority of new user=
s=20
today starts out by using gpg from the commandline.)

cheers
=2D- vbi

=2D-=20
No good deed goes unpunished.

--Boundary-02=_ZDYb/aYK+Dj/dBK
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iKcEABECAGcFAj9tgNlgGmh0dHA6Ly9mb3J0eXR3by5jaC9sZWdhbC9ncGcvZW1h
aWwuMjAwMjA4MjI/dmVyc2lvbj0xLjUmbWQ1c3VtPTVkZmY4NjhkMTE4NDMyNzYw
NzFiMjVlYjcwMDZkYTNlAAoJEIukMYvlp/fWtcgAnipBKFCMEC0Dm/xa3jd6BpaI
/DufAKDhFLGaQJoeY2aVuNiQEpR2SxjL8w==
=R6Vr
-----END PGP SIGNATURE-----

--Boundary-02=_ZDYb/aYK+Dj/dBK--