[Tickets #3017] NEW: Inconsitent MIME types in S/MIME-signed e-mail

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=3017
-----------------------------------------------------------------------
 Ticket             | 3017
 Created By         | voegele at trustsec.de
 Summary            | Inconsitent MIME types in S/MIME-signed e-mail
 Queue              | Horde Framework Packages
 Version            | HEAD
 State              | Unconfirmed
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


voegele at trustsec.de (2005-11-22 08:34) wrote:

Mutt fails to verify S/MIME-signed messages created with IMP.  The problem
is that the MIME type in the message header is "application/pkcs7-signature"
while the type of the actual MIME part is "application/x-pkcs7-signature". 
Note the "x-" in the second content type.

 Message header:

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

 MIME part:

 Content-Type: application/x-pkcs7-signature;
 name="smime.p7s"

I modified Crypt/Crypt/smime.php in the Horde framwork to fix this problem:

-        $smime_part->setContentTypeParameter('protocol',
'application/pkcs7-signature');
+       $smime_part->setContentTypeParameter('protocol',
'application/x-pkcs7-signature');

But maybe this bug should better be fixed within IMP.  I don't know. 
Anyway, the content types ought to be consistent.

Regards,
Andreas