Your message dated Sat, 5 Apr 2025 18:33:09 +0200
with message-id <[email protected]>
and subject line Re: Bug#526331: Auto-generate a revocation certificate?
has caused the Debian Bug report #526331,
regarding [gnupg2/1042] gnupg: auto-generate a revocation certificate
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
526331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526331
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnupg
Version: 1.4.9-4
Severity: wishlist
Given the number of times that I've witnessed clueless people
generate keys, publish them and then delete them, it would be good
if revocation certificates would be automatically generated and
mailed to them, or otherwise some sort of backup bundle should be
created with clear instructions for the people about their
importance and how to treat them.
E.g. a mail:
Dear user,
You have just generated a new GPG key on $HOSTNAME. For your
convenience, I've made a backup of the most important files in
$HOME/gpg-$KEYID-backup-$TIMESTAMP.zip . Please make a backup of
this file and keep it in a safe location. It is also a good idea
to print the revocation certificate contained in the ZIP archive
and store the printout separately. If someone else ever gains
control over your key, this is the only way you have to prevent
them from abusing your identity.
Cheers,
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gnupg depends on:
ii gpgv 1.4.9-4 GNU privacy guard - signature veri
ii libbz2-1.0 1.0.5-1 high-quality block-sorting file co
ii libc6 2.9-8 GNU C Library: Shared libraries
ii libreadline5 5.2-4 GNU readline and history libraries
ii libusb-0.1-4 2:0.1.12-13 userspace USB programming library
ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime
Versions of packages gnupg recommends:
ii libldap-2.4-2 2.4.15-1.1 OpenLDAP libraries
Versions of packages gnupg suggests:
pn gnupg-doc <none> (no description available)
ii imagemagick 7:6.5.1.0-1 image manipulation programs
pn libpcsclite1 <none> (no description available)
ii xloadimage 4.1-16.1 Graphics file viewer under X11
-- no debconf information
--
.''`. martin f. krafft <[email protected]> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
--- End Message ---
--- Begin Message ---
Version: 2.1.0-1
On 2009-04-30 martin f krafft <[email protected]> wrote:
> Package: gnupg
> Version: 1.4.9-4
> Severity: wishlist
> Given the number of times that I've witnessed clueless people
> generate keys, publish them and then delete them, it would be good
> if revocation certificates would be automatically generated and
> mailed to them, or otherwise some sort of backup bundle should be
> created with clear instructions for the people about their
> importance and how to treat them.
[...]
gpg v2.1v vand later does this:
gpg: directory '/home/testit/.gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as
'/home/testit/.gnupg/openpgp-revocs.d/63EBE2955CF0310C6A586DE1E1F381638D7E51F2.rev'
cu Andreas
--- End Message ---
