290369 - ssl connection dropped when "domain name mismatch" dialog appears.

Status: RESOLVED EXPIRED

(Core :: Security: PSM, defect)

Description

[pquiring]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

When connecting to a webserver on local network using a cert with the wrong
domain name, the dialog "domain name mismatch" appears.  But before I click on
OK to continue the ssl connection is already dropped.  "netstat -an" shows the
socket in FIN_WAIT_2 state while the dialog is present.  After clicking ok,
FireFox seems to be trying to download content but the socket is not connected.
Connecting to the site without ssl works fine.
IE6.0 has no problem with domain name mismatch.
The domain name is _DOMAIN_ (just a generic name I use for certs).

Reproducible: Always

Steps to Reproduce:
1.Type URL "https://10.1.2.1"
2.Dialog "domain name mismatch" appears.
3.Click OK, nothing happens.
Actual Results:  
ssl connection dropped.

Expected Results:  
Maintain ssl connection.

Comment 1

[Wan-Teh Chang]

Changed product to Core: Security:PSM.

Comment 2

[pquiring]

This problem doesn't seem to occur when connecting to a local (127.0.0.1) webserver.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.