Closed Bug 152382 Opened 23 years ago Closed 22 years ago

Crash opening Cert Manager with cert and FIPS enabled

Categories

(Core Graveyard :: Security: UI, defect, P1)

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Platform:
x86
Windows 2000
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME
Milestone:
psm2.4

People

(Reporter: junruh, Assigned: ssaux)

References

Details

(Keywords: crash)

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.
Blocks: fips
Keywords: nsbeta1
Does it work when you set a master password first?
This is still happening exactly as described. You have to setup a master password in order to get a cert.
Keywords: crash
Keywords: nsbeta1 → nsbeta1+
Priority: -- → P1
Target Milestone: --- → 2.4
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?
WFM. I do not crash when following the originally described steps.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
V
Status: RESOLVED → VERIFIED
Product: PSM → Core
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.