On Mon, 02 May 2005 12:28:15 +0300, Lars Wirzenius said:
> I've no idea what happened. The is supposed to have key id AF79D29E
> and importing it from the key server I use works fine.
There is a bad formatted signature in the key:
:signature packet: algo 17, keyid 432843E0AF3C67EA
version 4, created 1095417478, md5len 0, sigclass 10
digest algo 2, begin of digest c6 a9
hashed subpkt 2 len 4 (sig created 2004-09-17)
subpkt 16 len 8 (issuer key ID 432843E0AF3C67EA)
data: [158 bits]
data: [MPI_NULL]
^^^^^^^^^^
Current GnuPG versions bail out due to this (the length given in the
header of the MPI exceeds the length of the signature packet). In the
last weeks the problem occurred more and more and thus I changed the
code to behave more gracefully. The current CVS version will do
gpg: armor header: Version: GnuPG v1.0.6 (GNU/Linux)
gpg: mpi larger than indicated length (22 bytes)
gpg: read_block: read error: invalid packet
gpg: no valid OpenPGP data found.
gpg: import from `[stdin]' failed: invalid keyring
gpg: Total number processed: 0
on --import. This is better than before but we still need to change it
further to skip such invalid signature packets.
Shalom-Salam,
Werner
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
