Your message dated Fri, 8 May 2009 12:37:00 +0200 (CEST)
with message-id <[email protected]>
and subject line Bug#155541: disabled keys should be selected against in user
ID searches
has caused the Debian Bug report #155541,
regarding disabled keys should be selected against in user ID searches
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.)
--
155541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=155541
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: gpg
severity: normal
I have two keys for user shadow:
pub 512R/71EC9367 1994-04-12 Derrick J. Brashear <[email protected]>
pub 2048R/19353BE1 2002-07-26 Derrick J Brashear <[email protected]>
The 512-bit key is disabled because really that's a bit on the overly weak
side. and I'd rather not encrypt messages to that key.
However, it is the default key to get selected when I choose that user id:
gpg -e -r shadow /etc/motd
gpg: shadow: skipped: public key is disabled
gpg: no valid addressees
gpg: /etc/motd: encryption failed: no such user id
hartm...@konishi-polis:hartmans(2)>
That's kind of stupid. Instead, what should happen is that disabled
keys should be selected for string username matches only if no
non-disabled key exists.
Note that I see the same failure if I try encrypting to
[email protected].
--- End Message ---
--- Begin Message ---
This big seems to have been fixed. I tried to reproduce the issue and after
disabling
the "first" key, it was not longer chosen by gpg as default.
Please reopen your report if you observe a different result.
Regards, Daniel
--- End Message ---
