| Summary | Inconsitent MIME types in S/MIME-signed e-mail |
| Queue | Horde Framework Packages |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | slusarz (at) horde (dot) org |
| Requester | voegele (at) trustsec (dot) de |
| Created | 11/22/2005 (7246 days ago) |
| Due | |
| Updated | 11/23/2005 (7245 days ago) |
| Assigned | 11/22/2005 (7246 days ago) |
| Resolved | 11/23/2005 (7245 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
content-type parameters to pkcs7-*. Unfortunately, PHP's
openssl_pkcs7_* functions are "broken" in this regard so we have to do
a bit more search/replace to fix this. This has been fixed in HEAD
and 3.1.
State ⇒ Assigned
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Inconsitent MIME types in S/MIME-signed e-mail
Queue ⇒ Horde Framework Packages
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