[Pkg-gnupg-maint] Bug#514623: Cannot use revoked subkeys for decription using a smart card
Werner Koch
wk at gnupg.org
Tue Feb 10 09:33:18 UTC 2009
On Tue, 10 Feb 2009 00:04, enrico at debian.org said:
> revocation. Here's a simple use case for revocation without
> compromission: I revoke a 1024b subkey because I've switched to a 4096b
As well as a bunch of other reasons. Gpg even offers some standard
choices:
0 = No reason specified
1 = Key has been compromised
2 = Key is superseded
3 = Key is no longer used
Reasons 2 or 3 are Enrico's case, reason 0 is commonly used for
revocations created along with the key (usually means: I lost my
passphrase ;-).
> Why shouldn't I be allowed to use it to read my own old encrypted data,
> maybe (here's another quite legitimate use case) in order to reencrypt
You should be abale to do this. This seems to be a bug in GnuPG. If
you hurry and copy your report to bugs.gnupg.org, you will GnuPG bug
#1000 assigned ;-).
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
More information about the Pkg-gnupg-maint
mailing list