Closed
Bug 196147
Opened 21 years ago
Closed 21 years ago
Cannot open Preferences or View Page Info after accepting a self-sign certificate permanently
Categories
(Core Graveyard :: Security: UI, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: kent.tong.mo, Assigned: ssaux)
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130 After accepting a self-sign certificate permanently in the browser and viewing the root CA certificate in Preferences | Security, I can no longer open Preferences or View Page Info (on any page). The browser simply hangs when I try to do so. I am not sure if it matters. When I viewed the root CA certificates, I closed the Preferences window first and then close the "certificate manager" (not sure if this is the right name). Reproducible: Always Steps to Reproduce: 1. Open browser or Mozilla mail. 2. choose Edit | Preferences. Actual Results: It hangs. Expected Results: Open the Preferences window.
Can you provide a copy of the self-sign certificate in question, and how you made it / found it?
Comment 2•21 years ago
|
||
-> PSM
Assignee: mstoltz → ssaux
Component: Security: General → Client Library
Product: Browser → PSM
QA Contact: carosendahl → junruh
Version: Trunk → unspecified
Comment 3•21 years ago
|
||
Something else to try would be to upgrade to 1.3b, in a new dirctory of course.
Version: unspecified → 2.4
I don't have the self-sign certificate any more because I have replaced it with a real certificate. The only copy left is the one stored some where by Mozilla. I use openssl to create the key and the self-sign certificate: 1. openssl genrsa -out file.key 1024 2. openssl req -new -key file.key -x509 -out file.crt As far as I can tell, Mozilla imported this certificate just fine and I could (once) see it listed as a trusted root CA certificate and expanded the cert to see its details.
Comment 5•21 years ago
|
||
WFM. I followed the steps in comment #4, and didn't run into any problems.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Possibly related bugs: bug 204883 bug 196147 [this one] bug 205124 caused by bug 191524?
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
•