Crash opening Cert Manager with cert and FIPS enabled

VERIFIED WORKSFORME

Status

Core Graveyard
Security: UI
P1
normal
VERIFIED WORKSFORME
16 years ago
a year ago

People

(Reporter: John Unruh, Assigned: Stephane Saux)

Tracking

(Blocks: 1 bug, {crash})

1.0 Branch
psm2.4
x86
Windows 2000
crash

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
1.) With a new profile, obtain a cert - 
https://lab212sun.mcom.com:444/DirUserEnroll1024.html
2.) Open Device Manager, enable FIPS, and click OK.
3.) Open Cert Manager.
What happens: Crash. ID 
http://climate.netscape.com/reports/incidenttemplate.cfm?bbid=7434337
If you do not get a cert first, and just follow steps 2 and 3, you will not 
crash.

Updated

16 years ago
Blocks: 157795

Updated

16 years ago
Keywords: nsbeta1

Comment 1

16 years ago
Does it work when you set a master password first?
(Reporter)

Comment 2

16 years ago
This is still happening exactly as described. You have to setup a master 
password in order to get a cert.
Keywords: crash

Updated

16 years ago
Keywords: nsbeta1 → nsbeta1+

Updated

16 years ago
Priority: -- → P1
Target Milestone: --- → 2.4

Comment 3

16 years ago
related: with FIPS mode enabled, I couldn't go to an internal SSL website that
was signed by Thawte.

enabling FIPS mode seems to really goof things up with your smartcard loaded. 
Perhaps some interactions?
(Reporter)

Comment 4

15 years ago
WFM. I do not crash when following the originally described steps.
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 5

15 years ago
V
Status: RESOLVED → VERIFIED

Updated

13 years ago
Component: Security: UI → Security: UI
Product: PSM → Core

Updated

10 years ago
Version: psm2.3 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.