gpg 2.0.11 reports invalid packets on keys from gpg 1.4.9 and keyservers
Werner Koch
wk at gnupg.org
Mon May 25 10:42:36 CEST 2009
On Sat, 23 May 2009 07:47, john.marshall at riverwillow.com.au said:
> Please note that in an endeavour to eliminate discussion about
> keyservers and armor, I believe I have reduced this to a pure GnuPG
> native export/import issue across versions.
Can you please send me that key by PM? I just build a vanilla 2.0.11
and imported my copy of the key without problems:
$ GNUPGHOME=`pwd` sh
sh-2.05b$ ./gpg2 -k
gpg: WARNING: unsafe permissions on homedir `/foo/gnupg-2.0.11/g10'
gpg: keyring `/foo/gnupg-2.0.11/g10/pubring.gpg' created
gpg: /foo/gnupg-2.0.11/g10/trustdb.gpg: trustdb created
sh-2.05b$ ./gpg2 -v --import ~/anand.gpg
gpg: WARNING: unsafe permissions on homedir `/foo/gnupg-2.0.11/g10'
gpg: keyring `/foo/gnupg-2.0.11/g10/secring.gpg' created
gpg: pub 1024R/FC05DA69 1997-05-12 Anand xxxxxx
gpg: using PGP trust model
gpg: key FC05DA69: public key "Anand xxxxx" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
gpg: 1 keys cached (547 signatures)
gpg: 0 keys processed (0 validity counts cleared)
gpg: no ultimately trusted keys found
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
More information about the Gnupg-devel
mailing list