Closed Bug 197316 Opened 21 years ago Closed 18 years ago

Import of new CA Certificate fails on 1.3.

Categories

(NSS :: Libraries, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: binesh-mozilla, Unassigned)

References

()

Details

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

I have created my own certifying authority, and I _had_ imported it in
Mozilla-1.2.1, but, when I upgraded to 1.3, it doesn't show the certificate
anymore. What's even more odd, is that if I run Mozilla-1.2.1 _again_, I see the
certificate again, but, it disappears as soon as I go back to 1.3.

Reproducible: Always

Steps to Reproduce:
1. Well, I suppose you can just hit that URL, and see if it loads the
certificate. For me it APPEARS to succeed, but, then looking at Preferences |
Privacy & Security | Certificates | Manage Certificates | Authorities shows that
it isn't there...
Actual Results:  
The certificate isn't imported, (and there's no rationale given for why it
appears to succeed but, then fails)

Expected Results:  
Either tell me why it fails, or not fail to import.
>PSM
Assignee: asa → ssaux
Component: Browser-General → Client Library
Product: Browser → PSM
QA Contact: asa → bmartin
Version: Trunk → 2.4
This sounds like a bug in NSS.
Assignee: ssaux → wtc
Component: Client Library → Libraries
Product: PSM → NSS
QA Contact: bmartin → bishakhabanerjee
Version: 2.4 → unspecified
The URL above no longer works.  www.hex21.com doesn't resolve to an IP address.
Without access to that server (or some server that serves that CA cert), 
I cannot reproduce this behavior, and can only speculate on the cause.
Leaving unprioritized.
QA Contact: bishakhabanerjee → jason.m.reid
Assignee: wtchang → nobody
QA Contact: jason.m.reid → libraries
There's no bug here to reproduce.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.