Gnus development mailing list
 help / color / mirror / Atom feed
From: Vladimir Volovich <vvv@vsu.ru>
Subject: multipart s/mime signed
Date: Sat, 04 Aug 2001 16:02:16 +0400	[thread overview]
Message-ID: <eyr8usrq2f.fsf@vsu.ru> (raw)

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.



             reply	other threads:[~2001-08-04 12:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-04 12:02 Vladimir Volovich [this message]
2001-08-04 18:17 ` Florian Weimer
2001-08-05 13:21   ` Vladimir Volovich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eyr8usrq2f.fsf@vsu.ru \
    --to=vvv@vsu.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).