Re: [Sks-devel] Debugging a corrupted key

[Jim Popovitch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Wed, 2019-03-06 at 16:29 -0500, Jeremy T. Bouse wrote:
> On 3/6/2019 12:01 PM, Jim Popovitch wrote:
> > On Wed, 2019-03-06 at 11:44 -0400, Jason Harris wrote:
> > > On Wed, Mar 06, 2019 at 09:57:58AM -0500, Jim Popovitch wrote:
> > > > Hello!
> > > > 
> > > > What are some investigative techniques to determine how my GPG key was
> > > > corrupted.
> > > > 
> > > > gpg --keyserver pool.sks-keyservers.net --recv-key
> > > > 0x3F1C1EF2E6019EAC646CE45227155EB4C45A2705
> > > > gpg: packet(13) too large
> > > > gpg: read_block: read error: Invalid packet
> > > > gpg: no valid OpenPGP data found.
> > > > gpg: Total number processed: 0
> > > Look at all the bad userids that need to be filtered out:
> > >   
> > 
> > http://keyserver.timlukas.de:11371/pks/lookup?op=index&search=0x3F1C1EF2E6019EAC646CE45227155EB4C45A2705
> > 
> > > Get and save the key for analysis:
> > >   
> > 
> > http://keyserver.timlukas.de:11371/pks/lookup?op=get&search=0x3F1C1EF2E6019EAC646CE45227155EB4C45A2705
> > 
> > > Then:
> > >    %pgpdump lookup | less
> > 
> > 
> > OK, now what. :-)
> > 
> > Ideally what I'm looking for is where did that bad key come from, what
> > was the
> > source of entry into the pool?
> > 
> > -Jim P.
> > 
> 
> I've also been taking a look and it appears to have occurred on more
> keys at least from what I can find... I've even found a uid on
> Kristian's 0x16e0cf8d6b0b9508 key that appears to have been corrupted as
> well but I didn't see it on the
> 0x94CBAFDD30345109561835AA0B7F8B60E3EDFAE3 key listed for
> server_contact. Quickest way to see it is when doing a keyserver search
> is with a vindex op call. I'm not sure if simply re-uploading a clean
> copy of the key will fix it or if it's essentially a key that's
> permanently corrupted in the network.

FWIW, I tried, and was unable, to drop and re-upload a clean copy of my key. 
The drop logged as if the key was removed, but a search found the corrupted
key remained.  I rebuild the DB and my key is presently clean, but I do find
others (address@hidden is one of them)

- -Jim P.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlyAPqwACgkQdRlcPb+1
fkXx2RAAihqT0BA5BVG7v/oD2xiQWPBtg5P8DQwqiJvrtdeCV7YZivezYNjM69Jx
EtRwwD9wayZVCAYum45B9K7dbO5c1LKeXAcKkgLz/VZrgEClIwhwwPL+Dn4K6/Ns
+xigZVykN4ofGCNpbA+AiYp5epe4sr5qVOl9YZ+t0yy5NjmcAGTTCPDu49toehPv
XN3jgHszz8wyfg8skLl8mluHL4aiaKjXuVUhU2cGiblwrJCBqLeBzl2xke3kyIr+
Cj5jyKdqbNk9ClSaOLVuU86HOzoxbed5k7SFIIGMFDGCCMk+GHfX6aE8U6OfGD/T
GT8icafAPWJufbMcgSmuglXwbaeq+qI2lHZuBlZuNdFuDxtTTKE+tKK38Ax5xAm0
Z7LIMS9MczxswNFizuEkY7gf5cv4Wr+gp/NyeHs1kDEiw8gfbhdSVeukrbjuCzrr
9UTFUghlBrcr0gcQGodF9PEsUsHmW7NPpxN7LXkUWbH4wFnpRaEnHuo3g3kNouS2
i0W3l7mYq/VJSn0ZFIQQf4ONzm6+sgIb9FR0f7R6W38nQtvTBj4NE5znStzi9N+C
MUT5vmt3O0PtbQw8utRh3cUftjVfDtEF7m3EnsrBHeb3H9zWKwhYBdggW/8f6AyI
TO5mAbNp7s8tRMyPGgYd+9jiZ9O/QEEVKtEDv1iyWa7SSoGbVmk=
=i3kN
-----END PGP SIGNATURE-----