Bug: --list-packets ignores second public key
Hauke Laging
mailinglisten at hauke-laging.de
Mon Dec 23 21:07:08 CET 2013
Hello,
I was just in a slightly embarrassing situation: I had a look with
gpg --list-packets
at the certificate(s) on
http://www.westphal.de/index.php?id=18
This is the (shortened) output:
:public key packet:
[...]
:user ID packet:
:signature packet:
[...]
:signature packet:
[...]
:user ID packet:
:signature packet:
[...]
:signature packet:
[...]
:user ID packet:
:signature packet:
[...]
:signature packet:
[...]
So I told the site owner that there was (in contrast to his statement above)
just one certificate on the page. I had to realize that gpg sees both public
keys when importing the block instead.
Hauke
--
Crypto für alle: http://www.openpgp-schulungen.de/fuer/unterstuetzer/
http://userbase.kde.org/Concepts/OpenPGP_Help_Spread
OpenPGP: 7D82 FB9F D25A 2CE4 5241 6C37 BF4B 8EEF 1A57 1DF5
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 572 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20131223/e46df6ad/attachment.sig>
More information about the Gnupg-users
mailing list