PSM crashes if FIPS-mode is enabled.

VERIFIED FIXED in psm2.0

Status

()

Core
Security: PSM
P1
critical
VERIFIED FIXED
18 years ago
10 years ago

People

(Reporter: Stephen Moehle, Assigned: Javier Delgadillo)

Tracking

({crash})

1.0 Branch
psm2.0
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
PSM will crash if FIPS-mode (on the Advanced tab of the Personal Security
Manager) is enabled and then disabled.

To reproduce:
1) Go to the Modules section on the Advanced tab of the Personal Security
Manager dialog.
2) Click on the Enable button next to the "Enable FIPS-mode" text. The button
should now say Disable and the text say "Disable FIPS-mode".
3) Close the Personal Security Manager dialog.
4) psm.exe will crash in a couple of minutes.  Unfortunately since it is psm
crashing and not Mozilla, no Talkback incident is created.

In addition, if after step 2, but before psm.exe crashes, you click on the
Disable button, the button disapears and is replaced by the text: "Not
Implemented. The requested feature has not been implemented, or is not
functioning properly."

Tested with Mozilla 122805 on NT4.

Comment 1

18 years ago
Confirmed in the 12/31 commercial trunk WinNT build.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 2

18 years ago
*** Bug 64308 has been marked as a duplicate of this bug. ***

Comment 3

18 years ago
Setting platforms to All.
Assignee: ddrinan → javi
Severity: normal → critical
OS: Windows NT → All
Priority: -- → P1
Hardware: PC → All

Comment 4

18 years ago
using 2001011804 win95 mtrunk.  

psm crashes upon first browser action after closing psm after enabling fips
mode.  rectifying the crash then prevents psm from loading subsequently, until
the browser is restarted.  after a browser restart following this crash, loading
psm shows that fips is no longer enabled.

here's what norton crashguard picks up:
Windows 95 Version 4.00.1111
PSM caused an invalid page fault in
module PSM.EXE at 014f:00449c2f.
Registers:
EAX=00000000 CS=014f EIP=00449c2f EFLGS=00010202
EBX=00899510 SS=0157 ESP=012afb14 EBP=00000000
ECX=00000001 DS=0157 ESI=008a3bf0 FS=2b2f
EDX=00000008 ES=0157 EDI=00000000 GS=0000
Bytes at CS:EIP:
8b 00 50 e8 19 e5 ff ff 83 c4 04 c3 8b 48 28 8b 
Stack dump:
00449c8f 012afb50 008a6840 008a3410 008102a0 008a3410 004498dc 008a3bf0 00424b4a
008a3bf0 00899510 008a69a8 008a6900 012aff94 81650db8 00000000 


suggest keyword crash.  if there's a such thing as a psm blocker, this'd be it.

Comment 5

18 years ago
Adding crash keyword
Keywords: crash, nsbeta1

Comment 6

17 years ago
Milestone 2.0
Target Milestone: --- → 2.0
Version: 1.4 → 2.0
(Assignee)

Comment 7

17 years ago
This should be fixed now.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED

Comment 8

17 years ago
Verified fixed.
Status: RESOLVED → VERIFIED

Updated

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

Updated

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