Bug 182029 - 1.4.2.1 breaks my keyring: "mpi larger than indicated length"
Summary: 1.4.2.1 breaks my keyring: "mpi larger than indicated length"
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnupg
Version: 4
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 182163
TreeView+ depends on / blocked
 
Reported: 2006-02-19 12:00 UTC by Enrico Scholz
Modified: 2007-11-30 22:11 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2006-07-12 19:35:23 UTC


Attachments (Terms of Use)

Description Enrico Scholz 2006-02-19 12:00:34 UTC
Description of problem:

After update to 1.4.2.1 my keyrings becomes unusable; now I get

| $ LANG=C gpg --update-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: buffer shorter than subpacket
| gpg: buffer shorter than subpacket
| gpg: signature packet without keyid
| gpg: buffer shorter than subpacket
| 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, PGP 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

Downgrading to 1.4.1 makes it work again. This issue (inclusive patch)
is described in
http://groups.google.com/group/linux.debian.bugs.dist/browse_frm/thread/4af65c6ae2efaa16/6a3c45eb7221960a


Version-Release number of selected component (if applicable):

gnupg-1.4.2.1-1

Comment 1 Nalin Dahyabhai 2006-02-20 21:01:54 UTC
Pushing a test update for this (1.4.2.1-3).  If there are no new bug reports by
Thursday, I'll move it to a Final update.

Comment 2 Nalin Dahyabhai 2006-07-12 19:35:23 UTC
That did happen.  Must have forgotten to close the bug report.


Note You need to log in before you can comment on or make changes to this bug.