Closed
Bug 281168
Opened 20 years ago
Closed 19 years ago
SSL Certificate not recognized although certificate issuer certificate issued by known CA
Categories
(Core Graveyard :: Security: UI, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: metihala, Assigned: KaiE)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Firefox (or Mozilla 1.7.3) doesn't seem to recognize any certification paths. In the example of www.verkkoposti.com there is a certificate that is issued by Thawte SGC CA. Thawte SGC CA is an unknown CA but its certificate is issued by VeriSign Class 3 Public Primary CA, which is recognized as a CA by Firefox. Internet Explorer doesn't recognize Thawte SGC CA either, but as it recognizes that its issuer certificate is issued by Verisign Class 3 Public Primary CA, it accepts the certificate of www.verkkoposti.com and the certification path shows Verisign Class 3 Public Primary CA -> Thawte SGC CA -> www.verkkoposti.com. Reproducible: Always Steps to Reproduce: 1. Browse to https://www.verkkoposti.com/e3/Identification?lang=en Actual Results: "Web Site certified by an Unknown Authority" window appears. Expected Results: Firefox should have recognized the certificate without asking the user to accept it.
Comment 1•20 years ago
|
||
-> PSM
Assignee: firefox → kaie
Component: General → Client Library
Product: Firefox → PSM
QA Contact: general
Comment 2•19 years ago
|
||
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 3•19 years ago
|
||
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•