On Sat, Jun 07, 2008 at 07:53:34PM +0200, Florian Kulzer wrote: > How does your DNS server resolve subkeys.pgp.net? I see five different > IP addresses, with preference given to either 213.239.206.174 or > 64.71.173.107. Try if you still have this problem when you specify one > of these IPs as the keyserver.
Ah ha! [EMAIL PROTECTED]:~$ gpg -v --keyserver 213.239.206.174 --recv-keys 73CDA455 gpg: requesting key 73CDA455 from hkp server 213.239.206.174 gpg: armor header: Version: SKS 1.0.10 gpg: pub 1024D/1880283C 2002-09-15 Anibal Monsalve Salazar <[EMAIL PROTECTED]> gpg: key 1880283C: removed multiple subkey binding gpg: key 1880283C: removed multiple subkey binding gpg: key 1880283C: invalid subkey binding gpg: key 1880283C: invalid subkey binding gpg: key 1880283C: invalid subkey binding gpg: key 1880283C: removed multiple subkey binding gpg: using PGP trust model gpg: key 1880283C: public key "Anibal Monsalve Salazar <[EMAIL PROTECTED]>" imported gpg: subpacket of type 20 has critical bit set gpg: 347 keys cached (53608 signatures) gpg: 1 keys processed (1 validity counts cleared) gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model gpg: NOTE: signature key 8B38A1AF expired Sat 13 Oct 2007 17:51:45 NZDT gpg: NOTE: signature key BED7BF43 expired Sun 25 May 2008 13:32:59 NZST gpg: NOTE: signature key E62FA358 expired Wed 12 Mar 2008 01:43:31 NZDT gpg: NOTE: signature key C3AB3F38 expired Wed 09 Jan 2008 04:28:24 NZDT gpg: subpacket of type 20 has critical bit set gpg: NOTE: signature key B1293F34 expired Sat 02 Feb 2008 23:30:11 NZDT gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u gpg: Total number processed: 1 gpg: imported: 1 Oooops: [EMAIL PROTECTED]:~$ gpg -v --keyserver 213.239.206.174 --recv-keys 330C4A75 gpg: requesting key 330C4A75 from hkp server 213.239.206.174 gpg: armor header: Version: SKS 1.0.10 gpgkeys: key 330C4A75 not found on keyserver gpg: invalid radix64 character 2E skipped gpg: invalid radix64 character 3A skipped gpg: invalid radix64 character 5F skipped gpg: invalid radix64 character 2E skipped gpg: invalid radix64 character 2E skipped gpg: invalid radix64 character 2D skipped gpg: invalid radix64 character 3A skipped gpg: invalid radix64 character 3B skipped gpg: malformed CRC gpg: read_block: read error: invalid keyring gpg: Total number processed: 0 Weird is this one, all subsequent tries exhibit same error as above. [EMAIL PROTECTED]:~$ gpg --keyserver 213.239.212.133 --recv-keys 330C4A75 gpg: requesting key 330C4A75 from hkp server 213.239.212.133 gpgkeys: key 330C4A75 not found on keyserver gpg: signature packet: unhashed data too long gpg: no valid OpenPGP data found. gpg: read_block: read error: invalid packet gpg: Total number processed: 0 subkeys.pgp.net A 221.133.213.196 subkeys.pgp.net A 64.71.173.107 subkeys.pgp.net A 195.113.19.83 subkeys.pgp.net A 213.239.206.174 subkeys.pgp.net A 213.239.212.133 Any others? So, 330C4A75 is the only one left which is problematic. Even from a new user the problem occurs. -- Chris. ====== "One, with God, is always a majority, but many a martyr has been burned at the stake while the votes were being counted." -- Thomas B. Reed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
