Tickets :: [#12430] S/MIME: Rarely signature failure if adding attachment

6.0.0-beta1

7/5/25

Summary	S/MIME: Rarely signature failure if adding attachment
Queue	IMP
Queue Version	6.1.2
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	lauffer (at) ph-freiburg (dot) de
Created	07/05/2013 (4383 days ago)
Due
Updated	07/16/2013 (4372 days ago)
Assigned	07/15/2013 (4373 days ago)
Resolved	07/16/2013 (4372 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

07/16/2013 12:09:51 PM	Jan Schneider	State ⇒ Not A Bug

07/16/2013 11:56:54 AM	lauffer (at) ph-freiburg (dot) de	Comment #3	Reply to this comment
Hi Michael , This sounds like something added by another system in the mailing chain. This isn't something IMP would do. And if so - this would be an error in PHP, since we don't generate the S/MIME data ourselves (it is done via the openssl_pkcs7_sign method). Ok, I see. Meanwhile I got the feedback that the user deleted his IMP identity and created a new one from scratch. After that the problem got solved. I would say we could close this ticket as invalid/solved. If I ever know what exactely caused the problem I would leafe a note here. Maybe (just maybe) we could do something in IMP/Horde to not get such a strange openssl_pkcs7_sign behaviour. Thanks!

07/15/2013 06:05:00 PM	Michael Slusarz	Comment #2 State ⇒ Feedback Priority ⇒ 1. Low	Reply to this comment
This sounds like something added by another system in the mailing chain. This isn't something IMP would do. And if so - this would be an error in PHP, since we don't generate the S/MIME data ourselves (it is done via the openssl_pkcs7_sign method).

07/05/2013 08:50:32 AM	lauffer (at) ph-freiburg (dot) de	Comment #1 Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ S/MIME: Rarely signature failure if adding attachment Queue ⇒ IMP Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
Hello! Atm we search for the reason why... but we can see this failure: If one of our users is adding an attachment to a s/mime signed mail the signature got broken (this is only the case if he adds an attachment!). If you look at the source of the mail you see the problem: Right near the end of the signed base64 part there is a newline. For example it looks like this: <<snip>> [...] JayliE7ts/PZyJ+457ZjNrOEavIdp5g+bmJc+kSbhSTLH2aNmrXCV7OYlh7Xwy+3s9uZX6zQ1CwQ eJgT4auOKTQZ13fPXNf18hig10ldbveKfdDo7lhlXCSUYl0hPuLnaunlz7/K/i0sUShebd3jn9Jk Q7hJ05ghz2EeSYT4Om+5p2PXQDhZsHWWxR55J7hWsA2pkEDlPGzYQoDusyC6Bt5qBsIBeIlXCJjZ guUoAAq5mwh2mfBaTJzmFmhr0M1SuMcDMCO68uL5fj9iZiKRBEvrHmc77DSsIZR7wxR1Y23YYm10 [...] <<snapp>> So if I delete the newline the mail is ok, signature valid. (strange, isn't it? maybe a invalid character somehow in the users identity profile... we are searching...)