Re: [Sks-devel] 0x80D0489D - bad MPI in pubkey packet

[Jason Harris]

On Sat, Oct 30, 2004 at 03:35:56PM -0400, Yaron Minsky wrote:

> This has now been fixed  by patch-33.  Said version is now running on
> sks.dnsalias.net.

> On Fri, 29 Oct 2004 13:58:23 -0400, Jason Harris <address@hidden> wrote:
> > 
> > 0x80D0489D, also available on the public LDAP keyservers, has a
> > bad MPI in the pubkey packet.  The current SKS hash is
> > 49540C8438C3DE14A5628F15540007C8, and the key dearmors the same

Although I haven't (yet) applied patch-33, your desire to keep unusable
keys/packets in SKS really bugs me.  Listing a raw keydump that includes
0x476B1681 causes mutt's pgpring to stop processing after:

  uid:q::::::::Rolf Bittner (Teleca Systems GmbH) <...>:
  sig:::17:FC3A58FE42D19081:2004-09-15:::::10:
  sig:::17:0FD6175DC60B008E:2004-09-23:::::10:
  sig:::17:2DB1D0B4476B1681:2003-11-04:::::13:
  sig:::17:2DB1D0B4476B1681:2004-06-04:::::13:

(purportedly hash 6202C291DE5608072CFA502C9941073E, which is apparently
followed by hash 620562E01A3E00C00DD8F8BAAC8A62B8)

and my SKS server even has problems creating a vindex of the key:

  Error handling request: Bit 7 of packet tag was not 1 as expected: 0

and doing an hget on it:

  Error handling request. Exception raised: Failure("Bit 7 of packet tag was 
not 1 as expected: 33")

While I don't see this on other servers, I can't even "sks drop" the key
to get rid of it:

  Handling DeleteKey
  <command handler> error in callback.: Failure("Bit 7 of packet tag was not 1 
as expected: 33")

Furthermore, hitting 0x80D0489D causes gpg to stop listing the contents
of my SKS keydump.  Keeping such garbage in SKS may be nice for research
purposes, but it really hoses all the wrong OpenPGP tools at present.

-- 
Jason Harris           |  NIC:  JH329, PGP:  This _is_ PGP-signed, isn't it?
address@hidden _|_ web:  http://keyserver.kjsl.com/~jharris/
          Got photons?   (TM), (C) 2004

pgpfKqLESjr78.pgp
Description: PGP signature