Closed Bug 255025 Opened 20 years ago Closed 19 years ago

persistent 'domain name mismatch' warning for certificates

Categories

(Core Graveyard :: Security: UI, enhancement)

Other Branch
x86
Linux
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 228684

People

(Reporter: hrosik, Assigned: KaiE)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040809
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040809

When accepting certificate issued by some other owner forever, the 'domain name
mismatch' warning still shows up (for the first time during each session - i.e.
till quitting Mozilla) even if certificate is marked as "accept permanently".
For example certificate issued by "pipni.cz" produces this warning when
accessing "mail.pipni.cz" even though accepted as trusted.

Reproducible: Always
Steps to Reproduce:



Expected Results:  
There should be some equivalent of 'accept permanently' (from the certificate
verification window) in the 'domain name mismatch' dialog.
Maybe someone could tell the site  owner to correct the problem instead
Severity: normal → enhancement
Or I could just stop using that site... :)
This problem arises from virtual servers - this and similar companies are
hosting some thousands domains and won't have certificate for each one of them.

Apart from that, I regard this as a kind of inconsistency in MMozilla behaviour
- if you say once you trust something, why should you be warned always - ok, why
not, but give me an option to turn it off.

BTW: 'Normal' priority is probably high however 'enhancement' seems to low to me.
This is rather annoying. My hosting site uses their ssl server certificate,
which is ok with me. I go to mail.mysite.com to login. Thunderbird gives me the
popup error window the first time I start it, every time. How hard would it be
to add the certificate to the ones provided with install??
*** Bug 276461 has been marked as a duplicate of this bug. ***
See bug 260037, bug 247476, bug 267923 - are these all the same?
Product: PSM → Core
*** Bug 260037 has been marked as a duplicate of this bug. ***
*** Bug 267923 has been marked as a duplicate of this bug. ***
*** Bug 286970 has been marked as a duplicate of this bug. ***

*** This bug has been marked as a duplicate of 228684 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.