corrupted keyring; now what is corrupted?

[folkert at vanheusden.com]

Hi,

I'm trying to write a program that fixes the keyring. I can read the
chain and do some sanity checks but I find nothing wrong.
So I ran gpg with some debugging switched on and then I get this:

...
gpg: DBG: parse_packet(iob=1): type=14 length=525 (search.../../g10/keyring.c.974)
gpg: DBG: parse_packet(iob=1): type=6 length=418 (search.../../g10/keyring.c.974)
gpg: DBG: parse_packet(iob=2005): type=6 length=418 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=13 length=39 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=70 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=70 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=76 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=76 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=76 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=76 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=76 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=76 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=76 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=98 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=106 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=13 length=43 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=103 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=13 length=44 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=70 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=70 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=76 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=76 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=76 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=76 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=76 (parse.../../g10/keyring.c.391)
gpg: DBG: parse_packet(iob=2005): type=2 length=76 (parse.../../g10/keyring.c.391)

gpg: Ohhhh jeeee: mpi crosses packet border
secmem usage: 1408/1408 bytes in 2/2 blocks of pool 1408/32768
Aborted

My question now is: what is this mpi crossing that packet border? Is this mpi-
data longer then what is in the packat? So a packet type ct == 6 || ct == 14 ||
ct == 5 || ct == 7 follows after the last one listed (right?) and the mpi-data
is bigger then that length-field? How can I see if an mpi is the correct length?


Folkert van Heusden

-- 
Auto te koop, zie: http://www.vanheusden.com/daihatsu.php
Op zoek naar een IT of Finance baan? Mail me voor de mogelijkheden.
--------------------------------------------------------------------
 UNIX admin? Then give MultiTail (http://vanheusden.com/multitail/) 
 a try, it brings monitoring logfiles to a different level! See     
 http://vanheusden.com/multitail/features.html for a feature-list.  
--------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE
Get your PGP/GPG key signed at www.biglumber.com!