Closed Bug 807551 Opened 13 years ago Closed 13 years ago

Thunderbird 16.0.2 is unable to send signed/encrypted mail

Categories

(Thunderbird :: Security, defect)

Product:
Thunderbird
Component:
Security
Version:
16 Branch
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 650355

People

(Reporter: dsoh, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20100101 Firefox/16.0 Build ID: 20121024073032 Steps to reproduce: We are using internal CA. Recently, it was noted that Thunderbird 16.0.2 is unable to send signed/encrypted mail. Actual results: 1) The CA cert is already imported into "Authorities"". It's make to identify websites, identify mail users and identify software makers. 2) Personal digital certificate (pfx file) from the Internal CA was installed into the "Your certificates" 3) Under "Account Settings" => Security, it was confirmed that the correct personal digital certificate was selected for signing and encrypting. When we try to send a signed/encrypted mail, got the following error?! "Sending of message failed. Unable to sign message. Please check that the certificates specified in Mail & Newsgroup Account settings for this mail account are valid and trusted. " So we try to manually import the public key (cer file) into "People" and got the following error? "This certificate can't be verified and will not be imported. The certificate issuer might be unknown or untrusted, the certificate might have expired or have been revoked, or the certificate might not have been approved." Expected results: Do note that there's no problem sending signed or encrypted mail using the digital cert in other mail clients like Microsoft Outlook.
Is this CA using md5 ?
Hi Ludovic, Yes. It's "MD5 With RSA Encryption".
Read the release notes - we've removed support for that. In Tools->options->Advanced there is aconfig editor button , click on it. filter md5 and flip the security.enable_md5_signatures That's a good work around. The real solution would be to generate new certs.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Hi Ludovic, Thanks a lot! That solved the problem.
You need to log in before you can comment on or make changes to this bug.