[solved] Re: gpg 2.0.11 reports invalid packets on keys from gpg 1.4.9 and keyservers

John Marshall john.marshall at riverwillow.com.au
Tue May 26 11:49:23 CEST 2009

On Tue, 26 May 2009, 10:29 +0200, Werner Koch wrote:
> An older libgcrypt actually showed the problem:
>   an mpi of size 0 is not allowed
>   an mpi of size 0 is not allowed
>   gpg: read_block: read error: Invalid packet
> thus finding the bug was easy after John sent me the full bad key.  The
> bug is due to an inconsistency between Libgcrypt and and GnuPG-1.4.
> That problem must have been there for many years and will be fixed in
> Libgcrypt 1.5.0.  For the time being I implemented a workaround in
> GnuPG.  It is already commited SVN to trunk; find a patch below.

Thank you Werner,

I re-built GnuPG 2.0.11 with a patched parse-packet.c on one of my
systems here and it now handles that key with no problem.

John Marshall
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: </pipermail/attachments/20090526/a1bfa737/attachment.pgp>

More information about the Gnupg-devel mailing list