bug with one key's private keys spread over several keyrings when signing keys

Daniel Kahn Gillmor dkg at fifthhorseman.net
Thu Jun 3 17:18:05 CEST 2010

On 06/03/2010 10:16 AM, Hagen Fürstenau wrote:
> You could argue that gpg should keep searching for a non-dummy primary
> key.

I would make this argument.

If gpg can distinguish dummy keys from non-dummy keys, and it has in its
posession a non-dummy version of the key in question, it is a bug to not
use it when the user requests it.

> Absent such a feature, the obvious workaround is to order your
> keyrings in such a way that the real primary key is found first.

I agree this is a workaround (and it looks like the OP has already
stumbled across it, as per the first message in this thread).

I would disagree with the characterization of this needed bugfix as a
"feature request", though.

Hauke, would you mind filing a bug about this at the project bugtracker
so it is at least on a to-do list someplace?


Thanks for the report.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 892 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20100603/ebb44b84/attachment-0001.pgp>

More information about the Gnupg-devel mailing list