[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sks-devel] Debugging a corrupted key
|
From: |
Jason Harris |
|
Subject: |
Re: [Sks-devel] Debugging a corrupted key |
|
Date: |
Wed, 6 Mar 2019 11:44:43 -0400 |
|
User-agent: |
Mutt/1.11.3 (2019-02-01) |
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
and/or:
%gpg --dearmor lookup
%mutt_pgpring -S -f -k lookup.gpg | less
--
Jason Harris | PGP: This _is_ PGP-signed, isn't it?
address@hidden _|_ Got photons? (TM), (C) 2004
signature.asc
Description: PGP signature