John W. Moore III wrote:
> While this would probably be a better Question on the Enigmail List; try
> File > Reload Key Cache from the Enigmail Key Management window.
I don't think Enigmail has anything to do with it. It is just passing the
gpg-error messages through.
Anyway, I tried you suggesti
David Shaw wrote:
> I don't think anyone here can help you without knowing what version of
> GnuPG you're talking about.
Oops, sorry.
I'm using GnuPG 1.4.3 on Slackware Linux (current tree).
Regards,
--
Ben Branders
web http://branders.name http://www.livre.nl
jabber
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ben Branders wrote
> Enigmail Keymanagement doesn't show any keys, not even the private ones.
>
> Please inform me what I should do to fix this.
> Thank you!
While this would probably be a better Question on the Enigmail List; try
File > Reload Key
On Sun, Apr 09, 2006 at 09:19:17PM +0200, Ben Branders wrote:
> Hi,
>
>
>
> Today I wanted to do an update of the public keys in my list via Enigmail
> (Refresh all public keys). I got this message:
>
> > gpg: MPI larger than indicated length (2 bytes)
> > gpg: keyring_get_keyblock: read error:
Hi,
Today I wanted to do an update of the public keys in my list via Enigmail
(Refresh all public keys). I got this message:
> gpg: MPI larger than indicated length (2 bytes)
> gpg: keyring_get_keyblock: read error: invalid packet
> gpg: keydb_get_keygblock failed: invalid keyring
I thought th
