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

Hauke Laging mailinglisten at hauke-laging.de
Thu Jun 3 15:47:56 CEST 2010


Am Donnerstag 03 Juni 2010 08:45:31 schrieb Hagen Fürstenau:

> According to the man page, --export-secret-subkeys does not omit the
> secret part of the primary key, but "renders it useless". IIUC the given
> keyrings are searched in order, and you have confirmed that it's indeed
> useless when found before the intact one.
> 
> GPG does not seem to have functionality to strictly "spread" a key over
> keyrings. So this would be a feature request, not a bug.

Considering the circumstances it really looks like a bug. Spreading keys works 
for encryption and the usage of a smartcard is a similar situation: main key 
here, subkeys there.

I have extended my tests:

start cmd:> LC_ALL=C gpg --no-default-keyring \
--secret-keyring ~/.gnupg/secondsecring.gpg \
--secret-keyring ~/.gnupg/secring.gpg \
--list-secret-keys 297AB799
Keyring: /home/hl/.gnupg/secondsecring.gpg
------------------------------------------
sec   1024R/0x297AB799 2010-06-02 [expires: 2010-06-05]
uid                    Smartcard Test <smartcardtest at hauke-laging.de>
ssb   1024R/0xF64B4F0F 2010-06-02 [expires: 2010-06-05]
ssb   1024R/0xF17AAD5B 2010-06-02 [expires: 2010-06-05]
ssb   1024R/0xD62B6574 2010-06-02 [expires: 2010-06-05]

Keyring: /home/hl/.gnupg/secring.gpg
------------------------------------
sec   1024R/0x297AB799 2010-06-02 [expires: 2010-06-05]
uid                    Smartcard Test <smartcardtest at hauke-laging.de>
ssb   1024R/0x92757F2A 2010-06-03 [expires: 2010-06-13]

There is an encryption key in the first keyring but gpg takes the (needed) one 
from the second keyring without problem.


CU

Hauke
-- 
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 555 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20100603/8c1d2cd9/attachment.pgp>


More information about the Gnupg-devel mailing list