On Thu, Feb 23, 2006 at 09:26:21AM +1100, Peter Howard wrote:
Sometime recently my gnupg keyring got stuffed. When I try to access
keys now I get the following output:
gpg: checking the trustdb
gpg: mpi larger than indicated length (2 bytes)
gpg: keyring_get_keyblock: read error: invalid packet
gpg: keyring_get_keyblock failed: invalid 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
gpg: validate_key_list failed
I haven't seen this symptom, but hope you've already fixed it. I'll
assume you've already updated to the latest version.
Keys which are already in the cache (like the one signing this mail) are
still accessible. But any new keys are imported fine, but then don't
appear for use; presumably it's using the last "good" cache.
Suggestions on what I should do now? Anyone know a way to "fix" the
keyring? Or should I just export my keys (pub and private), wipe the
keyring, and start over?
You could try installing the latest free(beer) Windows pgp or *x pgpi
you can find, and see if you can import the keyring there.
Comparatively few keys should be compatible with only one prog - most
should slide over just fine.
I used to make a habit of (occasionally) extracting each key to a
separate file. Something like that enables most of a keyring to be
reassembled, even if your trustdb needs to be redone.
--
Christopher Vance
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
