mutt/2139: messages with base64-encoded CRLF pgp bits can't be read
>Number: 2139
>Notify-List: 340116@xxxxxxxxxxxxxxx
>Category: mutt
>Synopsis: messages with base64-encoded CRLF pgp bits can't be read
>Confidential: no
>Severity: normal
>Priority: medium
>Responsible: mutt-dev
>State: open
>Keywords:
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Nov 21 21:41:36 +0100 2005
>Originator: Adeodato Simó
>Release: 1.5.11
>Organization:
>Environment:
>Description:
On Debian's Bug#340116 (http://bugs.debian.org/340116), Daniel Stone
reports that messages that are partially PGP-encrypted can no longer be
read by mutt, which fails with "Could not copy message".
>From what I understand, this is fixed with Brendan's following commit
(since I can't reproduce with current CVS):
2005-10-10 18:26:31 Brendan Cully <brendan@xxxxxxxxxx> (brendan)
* pgp.c: Make PGP decode failure non-fatal when displaying
messages (as opposed to decode-saving them). I think it would be
nicer to include the original text when decryption fails
though...
However, I myself was still experiencing the problem for some messages.
After a bit of investigation, I found out that Mutt was failing for
base64-encoded messages. For example, this one, created by Mutt itself:
http://people.debian.org/~adeodato/tmp/2005-11-21/base64.mbox
On further investigation, I saw that it only failed if the result of
base64-decoding the text contained CRLF. If one takes the above message,
and recodes the base64 chunk to not contain CRLF, it can be opened
without problems:
http://people.debian.org/~adeodato/tmp/2005-11-21/base64-nocrlf.mbox
Also, and with respect Daniel's original report, note that even if mutt
properly opens the message, it outputs somehow confusing messages.
First:
Could not decrypt PGP message
And then, when displaying:
PGP message successfully decrypted.
Sample message:
http://people.debian.org/~adeodato/tmp/2005-11-21/encrypted.mbox
>How-To-Repeat:
>Fix:
Unknown
>Add-To-Audit-Trail:
>Unformatted: