Closed Bug 803017 Opened 13 years ago Closed 13 years ago

Intermediate S/MIME certificate cannot be validated

Categories

(Thunderbird :: Security, defect)

16 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: u454259, Unassigned)

Details

Attachments

(2 files, 1 obsolete file)

1.73 KB, application/octet-stream
Details
1.95 KB, application/octet-stream
Details
Attached file Root CA (web.de) (obsolete) —
I was experimenting with S/MIME certificates. My e-mail provider (web.de) issues X.509 certificates. They also provide a root CA and an intermediate CA for e-mail certificates. Problem: I can import both CAs to TB's "Authorities" cert tab. But only the root CA seems to be valid (and only if trust it to "identify websites"). The intermediate CA appears invalid, no matter which trust seetings are applied to it or to the root CA. I'll attach both CA certs. The certificate chain is perfectly fine, e.g. if I import them into Windows' certificate management. Expected behavior: Thunderbird accepts both CAs as valid and - in turn - accepts S/MIME certificats signed by them.
Attached file Root CA (web.de) —
Attachment #672721 - Attachment is obsolete: true
Does it work if you switch security.enable_md5_signatures to true ?
Yes, it does. If set, the intermediate certificate is valid, as well as my private certificate. Thank you.
Adalbert, the fact the toggling the preference makes your certificate work, means that your email provider is using md5-based certificates. md5-based certificates are widely agreed no longer to be secure, so you should contact your provider and request a non-md5 certificate immediately as their security is at significant risk. Resolving as invalid, as this is an issue with the issued certificates rather than with Thunderbird.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: