Closed Bug 544213 Opened 16 years ago Closed 16 years ago

FIPS doesn't work in Shredder 3.2a1pre or Minefield 3.7a1pre

Categories

(Core :: Security: PSM, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 521849

People

(Reporter: nONoNonO, Assigned: KaiE)

Details

(Keywords: crash)

As commented in bug 512043 I cannot use FIPS with Shredder 3.2a1pre on Windows XP. When I create a new profile, enter a master password and try to Enable FIPS on Tools|Options|Advanced|Certificates|Security Devices, nothing happens. When I use an existing profile with FIPS already enabled, I get an error message when starting Thunderbird: Could not initialize the application's security component... Don't know if it matters, but I installed Shredder in a new directory.
Onno what's the status for that in Firefox 3.7 ?
In Minefield starting with a new profile and trying to Enable FIPS doesn't work either and using an old profile with FIPS enabled gives same error message as above and immediately crashes, before browser window is shown: http://crash-stats.mozilla.com/report/index/bp-3f742c41-3b6c-438f-8dbc-be7ec2100204
Assignee: nobody → kaie
Component: Security → Security: PSM
Product: Thunderbird → Core
QA Contact: thunderbird → psm
Summary: FIPS doesn't work in Shredder 3.2a1pre → FIPS doesn't work in Shredder 3.2a1pre or Minefield 3.7a1pre
0 ntdll.dll RtlEnterCriticalSection 1 nspr4.dll PR_Lock nsprpub/pr/src/threads/combined/prulock.c:233 2 xul.dll nsAutoLock::nsAutoLock obj-firefox/dist/include/nsAutoLock.h:219 3 xul.dll nsSSLIOLayerHelpers::isKnownAsIntolerantSite security/manager/ssl/src/nsNSSIOLayer.cpp:2230 4 xul.dll nsSSLIOLayerSetOptions security/manager/ssl/src/nsNSSIOLayer.cpp:3501 5 xul.dll nsNSSShutDownPreventionLock::~nsNSSShutDownPreventionLock security/manager/ssl/src/nsNSSShutDown.cpp:472 6 xul.dll nsSSLIOLayerNewSocket security/manager/ssl/src/nsNSSIOLayer.cpp:2250
Severity: normal → critical
blocking2.0: --- → ?
Keywords: crash
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
blocking2.0: ? → ---
You need to log in before you can comment on or make changes to this bug.