Bug 88111 - mutt doesn't handle revoked uids of gnupg keys correctly
mutt doesn't handle revoked uids of gnupg keys correctly
Product: Red Hat Linux
Classification: Retired
Component: mutt (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 2003-04-05 15:50 EST by Peter J. Holzer
Modified: 2014-03-16 22:35 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-04-07 17:19:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter J. Holzer 2003-04-05 15:50:37 EST
Description of problem:

When you try to send an GnuPG-encrypted message to a key with multiple uids,
where (at least) one uid has been revoked but (at least) one uid is still valid,
mutt incorrectly displays the whole key as revoked and refuses to encrypt and
send the message.

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


How reproducible:

Steps to Reproduce:
1. Find a public key on your key ring with at least one revoked uid and one
valid uid. (Alternatively, create a new key with two uids and revoke one of them).
2. Compose a message to the owner of the key, Choose P)gp - B)oth (sign+encrypt)
3. Try to send the mail
Actual results:

In the key selection menu, both uids of the key are marked with an "R"
(revoked). If you choose the key anyway, mutt complains that the key has been
revoked and refuses to encrypt and send the message.

Expected results:

Only the revoked uid should be marked as revoked. Sending mail encrypted with
that public key should still be possible.

Additional info:

Proposed fix:

Upgrade to mutt 1.4.1. The source RPM mutt-1.4.1-0.8.x.src.rpm is missing one
BuildPrereq (cyrus-sasl-devel), but otherwise compiles fine on Redhat 7.3 and
seems to work fine (not yet much tested, though).
Comment 1 Bill Nottingham 2003-04-07 17:19:44 EDT
We are probably not at this point going to do a version upgrade of mutt for 7.3.

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