Issue with certain key

Christian Biere christianbiere at
Sat Feb 25 17:08:48 CET 2006

Christian Biere wrote:
> David Shaw wrote:
> > On Thu, Feb 23, 2006 at 06:55:02PM +0100, Christian Biere wrote:
> > > gpg: requesting key FC05DA69 from hkp server
> > > gpg: mpi larger than indicated length (2 bytes)
> > > gpg: read_block: read error: invalid packet
> > > gpg: Total number processed: 0
> > > gpg: no valid OpenPGP data found.
> > Yes.  There are corrupt signatures on that key.  GnuPG 1.4.3 has code
> > to skip the corrupt signatures rather than reject the whole key.
> I'll fetch GnuPG from CVS and retry.

I used 1.4.3rc1 because the auto* tools just hate me. This fixes
the problem with the key but I had to delete it from my keyring
in order to get rid of the warnings with 1.4.2. I thought 1.4.3
would discard the corrupt signatures during the import but I
guess it really just skips them at run-time.

By the way, it's probably a good idea to update the website with
respect to CVS. I fetched GnuPG from CVS just read that you're
using SVN since July.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
Url : /pipermail/attachments/20060225/31994401/attachment.pgp

More information about the Gnupg-devel mailing list