Tickets :: [#10285] S/MIME encryption produces unreadable message

6.0.0-beta1

11/7/25

Summary	S/MIME encryption produces unreadable message
Queue	IMP
Queue Version	5.0.7
Type	Bug
State	Resolved
Priority	2. Medium
Owners	Horde Developers (at) , slusarz (at) horde (dot) org
Requester	kd (at) tu-cottbus (dot) de
Created	06/28/2011 (5246 days ago)
Due
Updated	08/02/2011 (5211 days ago)
Assigned	06/28/2011 (5246 days ago)
Resolved	08/02/2011 (5211 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

08/02/2011 10:47:50 PM	Michael Slusarz	Comment #5 State ⇒ Resolved	Reply to this comment
Fixed in Horde_Crypt 1.0.5.

08/02/2011 10:47:29 PM	Git Commit	Comment #4	Reply to this comment
Changes have been made in Git for this ticket: ~~Bug #10285~~: Encrypted S/MIME data is already base64 encoded. 2 files changed, 6 insertions(+), 6 deletions(-) http://git.horde.org/horde-git/-/commit/5c14e5065a1747208ae70a1813fa98910a28ffa5

08/02/2011 10:31:50 PM	Michael Slusarz	Comment #3	Reply to this comment
Plus, the Content-Description is not MIME encoded. This was fixed by: commit 1219e2a89f4ad6f7075afc74f527c9e96e96b2de Author: Jan Schneider <jan@horde.org> Date: Mon Jul 18 14:53:49 2011 +0200 Fix setting the MIME part description charset.

06/28/2011 10:39:31 AM	Jan Schneider	Comment #2 State ⇒ Assigned Assigned to Horde Developers Assigned to Michael Slusarz	Reply to this comment
Confirmed. Plus, the Content-Description is not MIME encoded.

06/28/2011 08:28:06 AM	kd (at) tu-cottbus (dot) de	Comment #1 Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ S/MIME encryption produces unreadable message Queue ⇒ IMP Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
If I send myself a S/MIME encrypted message, the resulting message cannot be decrypted. It seems the message body is base64-encoded twice. If I extract the message body, do a base64_decode and feed the result in 'openssl smime -decrypt' all is ok.