#3639: Handling of inconsistent smime signed messages.
---------------------------------------------+----------------------
Reporter: chris | Owner: mutt-dev
Type: defect | Status: new
Priority: minor | Milestone: 1.6
Component: crypto | Version: 1.5.21
Keywords: patch, smime, s/mime, signature |
---------------------------------------------+----------------------
Some email clients generate s/mime multipart/signed emails with
inconsistent Content-Type headers. The Content-Type of such messages have
a protocol of "application/x-pkcs7-signature" whereas the Content-type of
the individual smime.p7s part is listed as "application/pkcs7-signature"
(without the "x-"). This discrepancy does not affect the validity of the
signature which can be manually verified with openssl. However, mutt wont
even attempt verification of the signature because the mismatched Content-
Type of the message and the smime.p7s part causes an "Inconsistent
multipart/signed structure!" error before verification can occur.
This issue is present in both 1.5.21 and tip.
In this situation, it is more important to determine the validity of the
email's signature rather than reject it out-of-hand due to an idiosyncrasy
of the sender's client. I've attached a patch that should do just that
without sacrificing too much in the way of consistency checking.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3639>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
