Closed Bug 1443455 Opened 7 years ago Closed 7 years ago

Thunderbird is altering base64-encoded attachment part -> breaks S/MIME signature

Categories

(Thunderbird :: Untriaged, defect)

Product:
Thunderbird
Component:
Untriaged
Version:
52 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1216951

People

(Reporter: sandoz, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20180123215146 Steps to reproduce: I compose a message and add a 1.4 MB PDF file as an attachment and mark the mail as digitally signed. I *save* the message in the Drafts folder (IMAP). Actual results: When I open the Drafts folder and agree to download the attachment to verify the signature, it's broken. Expected results: The signature should be correct and the attachment not altered. The reason, why the signature is broken is an extra 0A (\n) character after a regular 0D0A (\r\n) line ending somewhere in the base64 encoded attachment section. The position differed sometimes I noticed. This happened without sending the mail, with different (but big enough) PDFs. This happened upon receiving mail from somebody else. It did not happen always. It appeared to me as if the order of attaching, marking for signing and filling the To: field seemed to changed the probability of this happening. I could not reproduce this with Thunderbird 59-BETA.
Summary: Thunderbird is corrupting attachments → Thunderbird is altering base64-encoded attachment part -> breaks S/MIME signature
Will be fixed in bug 1216951 soon.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Summary: Thunderbird is altering base64-encoded attachment part -> breaks S/MIME signature → Thunderbird is corrupting attachments
Summary: Thunderbird is corrupting attachments → Thunderbird is altering base64-encoded attachment part -> breaks S/MIME signature
You need to log in before you can comment on or make changes to this bug.