GNU bug report logs -
#42637
27.0.91; mm-view-pkcs7 doesn't handle S/MIME signed andd encrypted messages
Previous Next
Reported by: "Timothy J. Miller" <tmiller <at> mitre.org>
Date: Fri, 31 Jul 2020 16:20:02 UTC
Severity: normal
Tags: fixed
Found in version 27.0.91
Fixed in version 28.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Got some free time so I rebuilt. The CR/LF patch looks like it's working.
However, the S/MIME signature status/trust marking in the article body are missing for signed+encrypted. I went through a slew of old encrypted messages and most look like non-MIME messages. Occasionally one will present with a text/plain attachment, but most not. Attachments also seem to be decoding properly but I didn't test all examples, just spot checked a couple where the attachment got saved out as corrupted base64.
If I could add to the feature backlog, it would be nice to have a status mark for encrypted emails similar to the signature trust status marking.
-- T
On 8/4/20, 11:11, "Lars Ingebrigtsen" <larsi <at> gnus.org> wrote:
Timothy J Miller <tmiller <at> mitre.org> writes:
> Sometimes, but I usually get a block of Base64 text. I'll capture
> some samples tonight.
Hm. I only got blank messages...
Anyway, I found the problem -- Outlook used CRLF line endings on the
encrypted message itself, which messed up the parsing of the parts.
This should now be fixed in Emacs 28 (I'm pretty sure the CRLF->NL
transform is safe there -- there can't be binary parts that aren't
content-transfer-encoded, I think?)
But since you're seeing something else, perhaps there's more than one
bug here. Can you do a new "git pull" and test?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
This bug report was last modified 4 years and 316 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.