multipart s/mime signed

multipart s/mime signed

[Vladimir Volovich]

Hi,

when i send the following MML message:

  <multipart sign=smime keyfile="/home/vvv/.certs/vvv-cert.pem" type=signed>
  This is a test.
  <part type="application/octet-stream" filename="/path/to/filename.txt" disposition=attachment>
  </part>
  </multipart>

gnus generates an incorrect MIME message:

| To: ...
| Subject: ...
| From: Vladimir Volovich <vvv@vsu.ru>
| Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
|  micalg=sha1; boundary="----B74C59615493C8D84A8F6A42196B2EF2"
| 
| This is an S/MIME signed message
| 
| ------B74C59615493C8D84A8F6A42196B2EF2
| Content-Type: multipart/signed; boundary="=-=-="
| 
| --=-=-=
| Content-Type: text/plain; charset=koi8-r
| Content-Transfer-Encoding: quoted-printable
| 
| This is a test.
| 
| --=-=-=
| Content-Type: application/octet-stream
| Content-Disposition: attachment; filename=filename.txt
| 
|  .....
| 
| --=-=-=--
| 
| ------B74C59615493C8D84A8F6A42196B2EF2
| Content-Type: application/x-pkcs7-signature; name="smime.p7s"
| Content-Transfer-Encoding: base64
| Content-Disposition: attachment; filename="smime.p7s"
| 
|  .....
| 
| ------B74C59615493C8D84A8F6A42196B2EF2--

The bug is that the Content-Type of the signed message is
  Content-Type: multipart/signed; boundary="=-=-="
instead of
  Content-Type: multipart/mixed; boundary="=-=-="

As a result, gnus displays this message as

  [[S/MIME Signed Part:Undecided]]
  [[Unknown Signed Part:Undecided]]
  This is a test.
  [2. application/octet-stream; passwd]...
  
  [[End of Unknown Signed Part]]
  [3. application/x-pkcs7-signature; smime.p7s]...

  [[End of S/MIME Signed Part]]

instead of

  [[S/MIME Signed Part:Undecided]]
  This is a test.
  [2. application/octet-stream; passwd]...
  
  [3. application/x-pkcs7-signature; smime.p7s]...

  [[End of S/MIME Signed Part]]

The situation is not better if i use the following MML:

  <multipart sign=smime keyfile="/home/vvv/.certs/vvv-cert.pem" type=signed>
  <multipart type=mixed>
  This is a test.
  <part type="application/octet-stream" filename="/path/to/filename.txt" disposition=attachment>
  </part>
  </multipart>
  </multipart>

BTW, should i explicitly use <multipart type=mixed> inside
<multipart sign=smime> to sign a multipart MIME message?

Best,
v.

Re: multipart s/mime signed

[Florian Weimer]

Vladimir Volovich <vvv@vsu.ru> writes:

>   <multipart sign=smime keyfile="/home/vvv/.certs/vvv-cert.pem" type=signed>

Try to leave out 'type=signed'.

Re: multipart s/mime signed

[Vladimir Volovich]

"FW" == Florian Weimer writes:

 FW> Vladimir Volovich <vvv@vsu.ru> writes:
 >> <multipart sign=smime keyfile="/home/vvv/.certs/vvv-cert.pem"
 >> type=signed>

 FW> Try to leave out 'type=signed'.

in this case i get

Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
 micalg=sha1; boundary="----C45FCE774A123BCEF94025404AC051EB"

This is an S/MIME signed message

------C45FCE774A123BCEF94025404AC051EB
Content-Type: multipart/mixed; boundary="=-=-="

--=-=-=
Content-Type: multipart/mixed; boundary="==-=-="

--==-=-=
Content-Transfer-Encoding: quoted-printable

This is a test.

--==-=-=
Content-Type: application/octet-stream
Content-Disposition: attachment; filename=filename.txt

(mixed inside mixed); and previewing this message is OK, but when i
press the verify button, the part numbers are changes from 2 3 to 5 6 :)

Best,
v.