Summary | Error in S/Mime Signing of messages |
Queue | Horde Framework Packages |
Queue Version | Git master |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | slusarz (at) horde (dot) org |
Requester | hordetest (at) trash-mail (dot) com |
Created | 12/04/2010 (5324 days ago) |
Due | |
Updated | 12/21/2010 (5307 days ago) |
Assigned | 12/21/2010 (5307 days ago) |
Resolved | 12/21/2010 (5307 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Resolved
mime messages, thus Horde_Mime_Part::parseMessage() fails to detect
the message header. I'm not sure what's the best way to fix it,
maybe to make sure that the Horde_Mime_Part passed to
Horde_Crypt_Smime doesn't use canonical line breaks and then adapt
the message parsing?
internally. So our only option is to convert/canonicalize after
grabbing the data from it.
Bug #9426: Fix S/Mime signingWorkaround broken openssl_pkcs7_sign() - it outputs both \r\n and \n in
the same string.
http://git.horde.org/horde-git/-/commit/6e30cda864a9971d1231cf38026dc5bd93713288
Assigned to Michael Slusarz
State ⇒ Assigned
Version ⇒ Git master
mime messages, thus Horde_Mime_Part::parseMessage() fails to detect
the message header. I'm not sure what's the best way to fix it, maybe
to make sure that the Horde_Mime_Part passed to Horde_Crypt_Smime
doesn't use canonical line breaks and then adapt the message parsing?
I tried that by setting 'canonical' to true in signMIMEPart() but it
didn't make a difference.
Queue ⇒ Horde Framework Packages
Version ⇒
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Error in S/Mime Signing of messages
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
non-object in /horde/framework/Crypt/lib/Horde/Crypt/Smime.php on line
252