Closed
Bug 152318
Opened 22 years ago
Closed 22 years ago
valid smime signature does not verify correctly
Categories
(MailNews Core :: Security: S/MIME, defect, P3)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 149272
People
(Reporter: g.iachello, Assigned: ssaux)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0) Gecko/20020530 BuildID: 2002053012 When I send a signed smime email to a mailing list and a single user, the mail signature is not correctly verified. When checking the message source (Ctrl-U) I noticed that the MIME subsection headers are strangely "formatted" (see additional information). Reproducible: Always Steps to Reproduce: 1. Get a personal SMIME certificate 2. Send a signed email to yourself and a mailing list you belong to 3. Check whether the signature on the mailing list message is valid Actual Results: The pencil icon on the received message, indicating the smime signature, is broken. Expected Results: The pencil icon, indicating the smime signature, should show that the signature was correctly verified. The following two snippets show what arrives to the recipient of the same message which was sent both to a user and a mailing list. In the first case the recipient is the single user, and the signature is valid. In the second, it is an MS Exchange mailing list, and Mozilla shows that the signature is invalid. As you can see, in the second snippet, the Content-type headers are formatted and the signature obviously does not verify correctly. The same message signature is correctly verified with MS Outlook. [...] To: Giovanni <go@libero.it>, vox <vox@test.it> [...] --------------ms060206030501080908030500 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Questa è una prova di messaggio firmato giac --------------ms060206030501080908030500 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJqjCC AzMwggKcoAMCAQICAwYHCDANBgkqhkiG9w0BAQIFADCBkjELMAkGA1UEBhMCWkExFTATBgNV --------------ms060206030501080908030500 Content-Type: text/plain; format=flowed; charset="UTF-8" Content-Transfer-Encoding: 8bit Questa è una prova di messaggio firmato giac --------------ms060206030501080908030500 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJqjCC AzMwggKcoAMCAQICAwYHCDANBgkqhkiG9w0BAQIFADCBkjELMAkGA1UEBhMCWkExFTATBgNV
Comment 1•22 years ago
|
||
S/MIME
Assignee: mstoltz → ssaux
Component: Security: General → S/MIME
Priority: -- → P3
Product: MailNews → PSM
QA Contact: junruh → carosendahl
Version: other → 2.3
Comment 2•22 years ago
|
||
Can you edit the mail preferences under composition and check the quoted printable option to see if that fixes your problem? I am curious to see if this is the same bug. thanks *** This bug has been marked as a duplicate of 149272 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•