Gnupg or keyserver bug?
wk at gnupg.org
Fri Jun 17 19:06:35 CEST 2005
On Fri, 17 Jun 2005 11:25:43 +0200, Kevin Bube said:
> | kevin at leibnitz:~/tmp $ gpg --keyserver blackhole.pca.dfn.de --homedir /tmp --recv-key EAE8EB6A
> | gpg: keyring `/tmp/secring.gpg' created
> | gpg: keyring `/tmp/pubring.gpg' created
> | gpg: requesting key EAE8EB6A from hkp server blackhole.pca.dfn.de
> | gpg: Ohhhh jeeee: mpi crosses packet border
This is due to a corrupted key received from that server. 1.4.2 will
print a more friendly diagnostic in such cases.
> | kevin at leibnitz:~/tmp $ gpg --keyserver subkeys.pgp.net --homedir /tmp --recv-key EAE8EB6A
Better keyservers remove such cruft before processing such keys. This
is the reason why you don't get the problem here. Old key server
software (hkp or keyserver.net stuff) can't cope with OpenPGP and
mangle keys. Don't use them.
More information about the Gnupg-devel