Closed
Bug 143071
Opened 24 years ago
Closed 24 years ago
Disable immediate FIPS switching
Categories
(Core Graveyard :: Security: UI, defect, P2)
Tracking
(Not tracked)
VERIFIED
WONTFIX
psm2.3
People
(Reporter: KaiE, Assigned: KaiE)
Details
Because of the arguments stated in bug 142659, I recommend that switching FIPS
mode during runtime should no longer be supported.
I suggest we remember the switch somewhere internally, and do the switch the
next time we start up. We should inform the user that a complete application
exit is required to do the switch.
| Assignee | ||
Comment 1•24 years ago
|
||
I suggest this should block bug 133584.
Comment 2•24 years ago
|
||
We should implement this for RTM.
| Assignee | ||
Comment 3•24 years ago
|
||
Situation has changed since my last comments.
Bob provided patches in bug 142659, that allowed me to produce a fix in bug
143532. With those patches, we might be safe already.
However, Bob said, we are not sure. Even with those patches, after having
toggled FIPS mode, we have still objects in memory, and their presence could
cause side effects we are not yet aware about.
Bob suggested, if we want to be really safe, we should implement this bug and
ask the user to restart.
| Assignee | ||
Comment 4•24 years ago
|
||
Because we are now avoiding immediate crashes, and the approach suggested in
this bug is a bit more work to implement, I had a chat with Stephane, and he
suggested that a release note might be sufficient.
Thinking more about it, I'd say instead of a release note, we also could just
display a restart recommendation message to the user.
I'm marking this bug as WONTFIX and have filed bug 148305 for adding the message.
Status: NEW → RESOLVED
Closed: 24 years ago
Keywords: nsbeta1+
Resolution: --- → WONTFIX
Whiteboard: [adt2 RTM]
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•