-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
HORNBOSTEL, LIBBY A (ATTSI) escribió:
> I have installed gpg4win version 1.1.4 with the following
> details/versions:
> GnuPG: 1.4.9
...
> I have installed GPGShell version 3.7.2 on top to maintain the keys with
> a gui interface. I have created ma
: mpi larger than indicated length
(258 bytes)'.
I have found the only references to this error back in the 2005-2006
timeframe and involving GnuPG version 1.4.2. I assume that version
1.4.9 (that I am using) would contain the fix that was used to correct
this issue.
Any ideas? Do I need to dele
Is there any chance this might have been fixed with the 1.4.3 release?
http://marc.theaimsgroup.com/?l=gnupg-devel&m=114694741924376&w=2
At the moment I don't really know how to otherwise fix my keyring.
Any thoughts?
cheers
--
Torsten
___
Gnupg-user
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:
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
3978
> data: [1024 bits]
> gpg: mpi larger than indicated length (0 bytes)
> data: [MPI_NULL]
>
> Can anyone shed some light on this?
> Do I need to regenerate my key and send my counter part the new public key?
> Or have I run into a compatibility issue with P
ata: [1024 bits]
gpg: mpi larger than indicated length (0 bytes)
data: [MPI_NULL]
Can anyone shed some light on this?
Do I need to regenerate my key and send my counter part the new public key?
Or have I run into a compatibility issue with PsypherOPS?
other data:
$ gpg --list-public-ke
10 matches
Mail list logo
