mpi error with check-trustdb in 1.4.2 - resolved
John Clizbe
JPClizbe at comcast.net
Thu Aug 11 05:30:09 CEST 2005
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John Clizbe wrote:
> Hi Werner, Dave, and everyone else.
>
> This error started showing up when I switched to 1.4.2. It does not occur in
> 1.4.1. A similar mpi error occurs with --rebuild-keydb-cache.
>
> It's not dangerous like some of the 1.4.0 rename errors, just a nuisance.
>
> Probably just key cruft, but I thought you might want to look at it since it
> wasn't a problem in prior versions.
Tracked down the two offending keys and deleted them with 1.4.1. They both
failed to import from a keyserver with 1.4.2 with the same mpi error, so I'm
marking it off to key cruft.
The keys were:
pub 1024R/FC05DA69 1997-05-12 Anand Kumria <akumria at acm.org>
pub 1024D/A0B3E88B 2000-07-24 Martin Pool <mbp at sourcefrog.net>
- --
John P. Clizbe Inet: JPClizbe(a)comcast DOT nyet
Golden Bear Networks PGP/GPG KeyID: 0x608D2A10
"Be who you are and say what you feel because those who mind don't matter
and those who matter don't mind." - Dr Seuss, "Oh the Places You'll Go"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: When cryptography is outlawed, b25seSBvdXRsYXdzIHdpbGwgdXNlIG
Comment: Be part of the £33t ECHELON -- Use Strong Encryption.
Comment: It's YOUR right - for the time being.
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFC+sZBHQSsSmCNKhARAvAIAKDMNYnzFhcbjL8+Wt58SOfbpOVjcgCgiCnv
/X23Es3Fwc/vbnLkDAsEszU=
=Uhd9
-----END PGP SIGNATURE-----
More information about the Gnupg-devel
mailing list