-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Me, too. :-/ I completely emptied my public keyring, one key at a time,
looking for the damage and never found it. Eventually I renamed the empty
file away and built a new one, and now I have no more trouble.
I don't know whether a keyring file is su
d length (2 bytes)
> > gpg: keyring_get_keyblock: read error: invalid packet
> > gpg: keydb_get_keyblock failed: invalid keyring
> > gpg: validate_key_list failed
> >
> > And the trustdb is not updated, because on the next run
> > I get the same error.
> >
&g
Peter Pentchev wrote:
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.
I'm using 1.4.2 built from ports on both a 7-current and 4-stable system,
with some pretty large keyrings, and haven't had these problems, FYI.
Doug
--
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
> > g
alid keyring
> gpg: failed to rebuild keyring cache: invalid keyring
> gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model
> gpg: mpi larger than indicated length (2 bytes)
> gpg: keyring_get_keyblock: read error: invalid packet
> gpg: keydb_get_keyblock failed: invalid
: keyring_get_keyblock: read error: invalid packet
gpg: keydb_get_keyblock failed: invalid keyring
gpg: validate_key_list failed
And the
