Re: [Sks-devel] Debugging a corrupted key

[Jim Popovitch]

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

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.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlx//OYACgkQdRlcPb+1
fkUMjw//ceuXz9Tx2wF78qmOJlJ6+t21seoknevi52Hnn/ePugq/za+PrZfUjmts
XrTDgEZDUdfeQN9Wf6Bg2Ew6FmA3GWVNDYl0xrLvVZDYaRA9BiRopi+UvEpSCw32
y/eOFuj5hquwt2g4QtSqEVvG0fVwLQi9BwieL1FWnoy8XIQY8aQd5HX/bqVv4VEZ
qai2zydRoFn3lWFhhU3IX7TWv2X8emTN9t6Hj1tagHyGNBhiPu69bvQRm/KbQB9z
+pfxVT62+WOxdys8ZCWdD68ROCzDe+HUIRGYmzLTso0LNmNhYbuzkFmbF7TCVYux
oH3ob96bIFjyPZzjEaRCQEleZpbyzFNt7IfdYsnPge27/KaZ3UEmODfV6Elb0ZW6
yUzw1418ZacyINuIlxtPuhgs0m1eDxMdIUkLp2gk4IRs3qzs2OEmR+6HsBusSO4I
L6f+5viWoL0EETATlR9OoQct1zdiVw2zYT0mNGxashGuR5ZVdKrjZsRU+XfAb3r1
qcQd5J6mMHwVeRyuqJ0Zhnte/lYxCjqI/vLct3YgbyACOw4UfXHW0DPj6sAfIymj
E0271b30KbStwuuRbhfw7FkZhozR2qlunV4mnv2Ua6fHVyNlCgALZxG8fbPTVT6a
M7JZJQBFBg6Lh5zEs7aHxSoU2X4dhBW6sH95Blkgs0r40IXqnZ8=
=syu2
-----END PGP SIGNATURE-----