jharris at widomaker.com
Mon Aug 8 20:25:27 CEST 2005
On Mon, Aug 08, 2005 at 12:33:07PM +0300, Peter Pentchev wrote:
> On Fri, Aug 05, 2005 at 04:15:47PM +0200, Thomas Klausner wrote:
> > After adding some keys recently, I always get:
> > gpg: mpi larger than indicated length (2 bytes)
> > gpg: keyring_get_keyblock: read error: invalid packet
> > gpg: keyring_get_keyblock failed: invalid keyring
> > How can I fix this?
> > Or how can I find out which key it is, so I can remove it
> > (as workaround)?
> FWIW, I've been getting the same with the FreeBSD port of gnupg-1.4.2.
> I've reverted to using 1.4.1 for the present.
Try running pgpring (part of mutt):
%pgpring -S -k ~/.gnupg/pubring.gpg
%pgpdump [-i] ~/.gnupg/pubring.gpg
on the keyring(s) to help find any corruption.
(I've not seen any such problems on FreeBSD 4.x with GPG 1.4.2.)
Jason Harris | NIC: JH329, PGP: This _is_ PGP-signed, isn't it?
jharris at widomaker.com _|_ web: http://keyserver.kjsl.com/~jharris/
Got photons? (TM), (C) 2004
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 313 bytes
Desc: not available
Url : /pipermail/attachments/20050808/c480e8c6/attachment-0001.pgp
More information about the Gnupg-users