Re: [Sks-devel] Invalid Packet on SKS 1.1.0 (SKS 1.0.10 OK)

[Phil Pennock]

On 2009-05-22 at 19:49 +1000, John Marshall wrote:
> Attempts to use GnuPG 2.0.11 to retrieve a particular key from any sks
> 1.1.0 keyserver fails with an "Invalid packet" error.  Retrieval of the
> same key from any 1.0.10 keyserver is successful.

I have gpg and gpg2 installed; gpg2 is 2.0.11 and I see the problem you
described, gpg is 1.4.9 and works fine.

If I export the packet from gpg1 and import with gpg2, using a local
file, I get a similar error, which leads me to suspect a regression in
gnupg2 at handling legitimate data, rather than sks.

% gpg -a --export 0xFC05DA69 > FRED1
% gpg2 --import FRED1
gpg: WARNING: This version has been built with support for the Camellia cipher.
gpg:          It is for testing only and is NOT for production use!
gpg: read_block: read error: Invalid packet
gpg: no valid OpenPGP data found.
gpg: import from `FRED1' failed: Invalid keyring
gpg: Total number processed: 0

[....]
gpg: DBG: iobuf-1.0: underflow: eof (no filter)
gpg: DBG: iobuf-1.0: close `(null)'
gpg: DBG: iobuf-*.*: ioctl `FRED1' invalidate
gpg: DBG: fd_cache_invalidate (FRED1)
gpg: DBG:                 did (FRED1)

pgpSbWRTNnoOG.pgp
Description: PGP signature