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

[John Marshall]

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.

The following command:
  gpg --keyserver <sks-1.1.0-keyserver-url> \
      --keyserver-options no-honor-keyserver-url \
      --recv-keys 0xFC05DA69

Results in:
  gpg: requesting key FC05DA69 from hkp server <sks-1.1.0-keyserver-url>
  gpg: read_block: read error: Invalid packet
  gpg: Total number processed: 0
  gpg: no valid OpenPGP data found.

The same command using any sks 1.0.10 keyserver works fine.

If I switch on debugging in gpg (--debug-all), I see this when talking
to a sks 1.1.0 keyserver:

  360 gpg: DBG: parse_packet(iob=1): type=2 length=540 (parse.import.c.376)
  361 gpg: DBG: parse_packet(iob=1): type=2 length=540 (parse.import.c.376)
  362 gpg: DBG: parse_packet(iob=1): type=13 length=42 (parse.import.c.376)
  363 gpg: DBG: parse_packet(iob=1): type=2 length=30 (parse.import.c.376)
  364 gpg: read_block: read error: Invalid packet

The same section of the debug output when talking to a sks 1.0.10
keyserver:

  360 gpg: DBG: parse_packet(iob=1): type=2 length=540 (parse.import.c.376)
  361 gpg: DBG: parse_packet(iob=1): type=2 length=540 (parse.import.c.376)
  362 gpg: DBG: parse_packet(iob=1): type=13 length=42 (parse.import.c.376)
  363 gpg: DBG: parse_packet(iob=1): type=2 length=63 (parse.import.c.376)
  364 gpg: DBG: parse_packet(iob=1): type=2 length=63 (parse.import.c.376)

I tried deleting the key from my (1.1.0) keyserver, watched it synch
back from a 1.0.10 keyserver, and tried again.  Same story.

Do we have a problem in 1.1.0?

-- 
John Marshall

pgp_HfLwWC_F6.pgp
Description: PGP signature