gpg2 handles 1024R keys incorrectly

Hirohisa Yamaguchi umq.461 at
Wed Oct 18 05:17:58 CEST 2006


While I'm testing gpg2 (1.9.92) on FreeBSD/amd64.
I got messages below a thousand times.

gpg: packet(2) too short
gpg: keyring_get_keyblock: read error: invalid packet
gpg: keydb_get_keyblock failed: invalid keyring

I removed pubring.gpg from ~/.gnupg and tried to rebuild it.

while adding 1024R keys (e.g. 0x16F4CCE9 from
I got following

$ gpg2 --verbose --recv-keys 0x16F4CCE9
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
Warning: using insecure memory!
gpg: requesting key 16F4CCE9 from hkp server
Version: SKS 1.0.9
gpg: armor header:
Sendmail Security <sendmail-security at>
gpg: pub  1024R/E9CCF416 1999-06-23
gpg: key E9CCF416: skipped user ID "Sendmail Security <sendmail-security at>"
gpg: key E9CCF416: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: Total number processed: 1
gpg:           w/o user IDs: 1

The key id 16F4CCE9 is shown as E9CCF416.
It seems that the byte-order was inverted somewhere.

I have not encountered this problem other than 1024R keys.


	Hirohisa Yamaguchi
	  umq.461 at

More information about the Gnupg-devel mailing list