Closed
Bug 377337
Opened 19 years ago
Closed 19 years ago
reported hostname mismatch with matching CN and subject alt DNS names
Categories
(Thunderbird :: Security, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 238142
People
(Reporter: dilyan.palauzov, Assigned: KaiE)
Details
Attachments
(1 file)
|
9.13 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: 1.5.0.7 (20060909)
I use TB1.5.0.7 (German), and try to send mails using a SMTP connection to smtp.aegee.org, over port 465 with SSL. Then TB sais something like: You are using certificate issued for smtp.aegee.org, but you are connecting to smtp.aegee.org . Would you like to continue?
The installed certificate is http://mail.aegee.org/~didopalauzov/07.pem and the error message is available at http://mail.aegee.org/~didopalauzov/smtp.aegee.org.PNG . It is in German, but I hope you will get the idea.
Reproducible: Always
| Reporter | ||
Comment 1•19 years ago
|
||
Comment 2•19 years ago
|
||
Confirming, very strange.
Off-topic: why are you not keeping up with the security fixes released for both Firefox and Thunderbird? There have been several important fixes in each product since the versions you are running. Updates should have been automatic.
Assignee: dveditz → kengert
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Reporter | ||
Comment 3•19 years ago
|
||
> Off-topic: why are you not keeping up with the security fixes
This is the software pre-installed in my university. I have no influence on updates.
| Reporter | ||
Comment 4•19 years ago
|
||
I moved now the whole to port 995, server smtp.aegee.org, connection over SSL. Please note, that connecting to mail.aegee.org, port 995 (same IP, same server, same port, same certficate) does not issue a warnin.
| Assignee | ||
Comment 5•19 years ago
|
||
Bob, Nelson, please see question after "obervation 1". Thanks.
So the reported problem is:
- Connection to SSL smtp.aegee.org port 955
- TB complains that "hostname does not match hostname", which does not make sense
I inspected the certificate in detail and I suspect I understand what is going wrong.
Your certificate has a "cert alt subject names" extension, which is marked as critical (application must understand extension or must reject cert).
The extension lists several host names as "DNS" names.
But smtp.aegee.org is not listed as an alternative name.
Usually, when certs do not have that extensions, we compare the CN (common name) field with the hostname that we connect to. And in your particular case, the CN seems to match the hostname.
So observation 1:
When critical alt subject DNS names are present, NSS seems to require a hostname match with an entry in the list, and NSS seems to ignore a good match with the CN field.
@Bob, @Nelson: Do you think that is correct behaviour or a bug in NSS?
Obervation 2:
The reason why the UI looks confusing is caused by the user interface implementation, which does not even look at the alt names extension. What happens is:
- mozilla calls NSS to verify cert
- NSS returns the decision "hostname mismatch"
- mozilla follows NSS' decision
- mozilla uses a simple strategy to bring up the error message, using CN field and hostname
Observation 3:
In comment 4 you mention that using DNS name mail.aegee.org (which points to the same server) you'll get a working connection.
This seems correct, because mail.aegee.org is listed as an alternative subject DNS name.
Summary: thunderbird does not recognize certificates issued for many sites → reported hostname mismatch with matching CN and subject alt DNS names
Comment 6•19 years ago
|
||
Re: Observation 1,
It's intentional. RFC 2818, which defines https, says:
If a subjectAltName extension of type dNSName is present, that MUST
be used as *the* identity. Otherwise, the (most specific) Common Name
field in the Subject field of the certificate MUST be used. Although
the use of the Common Name is existing practice, it is deprecated and
Certification Authorities are encouraged to use the dNSName instead.
Notice it doesn't say that the dNSName is ALSO used along with the Subject CN.
It says one or the other. This means that all intended dns names must be
listed in the SAN extension, not all-but-one in the SAN and one in the CN.
This is the single most commonly made mistake in certs issued by OpenSSL users.
Comment 7•19 years ago
|
||
This bug is a duplicate of bug 238142.
Comment 8•19 years ago
|
||
See also Bug 240261 which is relevant to this issue.
Also bug 94904.
| Assignee | ||
Comment 9•19 years ago
|
||
Thanks Nelson.
Reporter, in order to fix your system, please update your system to use a cert that includes the missing hostname in the dnsname extensions.
The remaining bug is the unhelpful error message, which should be resolved in bug 238142. Resolving as duplicate.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•