Reported Domain Name Missmatch - but actually CN and domain name are equal

RESOLVED DUPLICATE of bug 224179

Status

()

Core
Security: PSM
--
major
RESOLVED DUPLICATE of bug 224179
15 years ago
13 years ago

People

(Reporter: Dietmar Zlabinger, Assigned: Stephane Saux)

Tracking

Other Branch
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624

Using TLS/IMAP, when setting up connection I get an popup that 
the domain names would not match - but the text says "you attemted a connection
... with "myserver.wien.zlabinger.at" .. However security cert belongs to
"myserver.wien.zlabinger.at" (same name ?!)

doing the same with opera an OLE i do not get such an error-message,
tested with several certificats

Reproducible: Always

Steps to Reproduce:
1. setup imap/tls on port 993 at mail.eggern.at
2. accept cert
3. see error message

Actual Results:  
complain about CN to be wrong, but it is actually correct

Expected Results:  
accept CN=domain
(Reporter)

Comment 1

15 years ago
Created attachment 127447 [details]
screenshot
(Assignee)

Comment 2

15 years ago
mail.eggern.at that's the name that the mismatch. If you don't want a mismatch,
you need to use the same name in your imap config as the name in the cert that
the server will present.

There may be a bug in how we report the error.
The IMAPS server mail.eggern.at doesn't seem to be up.
I think the most likely explanation for the observed result it explained at 
http://bugzilla.mozilla.org/show_bug.cgi?id=224179#c9 
and so I am marking this bug as a duplicate of that one.

Reporter, if your cert did not have a subjectAltName, please reopen this bug

*** This bug has been marked as a duplicate of 224179 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → DUPLICATE

Updated

13 years ago
Component: Security: PSM → Security: PSM
Product: PSM → Core
You need to log in before you can comment on or make changes to this bug.