I am still trying to determine why Outlook(Valid) and Moz(Invalid) give
different results concerning the validity of a signed message's "Message
Integrity Check (MIC)".
How does Moz interpret RFC 1847 sec.2.1 "
"The multipart/signed content type contains exactly two body parts.
The first body part is the body part over which the digital signature
was created, including its MIME headers."
? Does Moz include INCLUDE|EXCLUDE the boundary line under the definition
of the "MIME headers".
It does not appear that the RFC gives a precise definition, nor actual
example. At the end of the section is the example with only the vague
textual description using 'MIME headers' terminology.
Content-Type: multipart/signed; protocol="TYPE/STYPE";
micalg="MICALG"; boundary="Signed Boundary"
* --Signed Boundary
*= Content-Type: text/plain; charset="us-ascii"
*=
*= This is some text to be signed although it could be
*= any type of data, labeled accordingly, of course.
*=
--Signed Boundary
Content-Type: TYPE/STYPE
CONTROL INFORMATION for protocol "TYPE/STYPE" would be here
--Signed Boundary--
Is the computed MIC over the lines marked with the '*' or the '='?
=== This next question concerns signature validation. Can|Does Moz handle a
signed message with the following structure? The 'first part' is a compound
part with embedded parts. It fits the 1847 definition of
"The first body part may contain any valid MIME content
type, labeled accordingly."
perl ../skeleton.pl < BrokenMsg.eml
Content-type: multipart/signed
Effective-type: multipart/signed
Body-file: NONE
Subject: 24 July Forum
Num-parts: 2
--
Content-type: multipart/alternative
Effective-type: multipart/alternative
Body-file: NONE
Num-parts: 2
--
Content-type: text/plain
Effective-type: text/plain
Body-file: msg-1027534853-1897-0/msg-1897-1.txt
--
Content-type: text/html
Effective-type: text/html
Body-file: msg-1027534853-1897-0/msg-1897-2.html
--
Content-type: application/x-pkcs7-signature
Effective-type: application/x-pkcs7-signature
Body-file: msg-1027534853-1897-0/smime.p7s
Recommended-filename: smime.p7s
--
This decomposition was produced with the MIME:: perl module.
Victor Probo
