Closed Bug 1736990 Opened 3 years ago Closed 3 years ago

Sandbox needs to expose /dev/random and /proc/sys/crypto/fips_enabled when running in FIPS mode

Categories

(Core :: Security: Process Sandboxing, defect, P3)

All
Linux
defect

Tracking

()

RESOLVED FIXED
96 Branch
Tracking Status
firefox95 --- wontfix
firefox96 --- fixed

People

(Reporter: msirringhaus, Assigned: msirringhaus)

References

Details

Attachments

(1 file)

For running in FIPS mode, NSS needs to check /proc/sys/crypto/fips_enabled, to be able to tell whether FIPS is enabled or not.
FIPS also mandates using /dev/random instead of /dev/urandom.

MediaPluginSandbox already exposes /proc/sys/crypto/fips_enabled, but not /dev/random.
Content- and SocketProcessPolicy expose neither.

For running in FIPS mode, NSS needs to check /proc/sys/crypto/fips_enabled, to be able to tell whether FIPS is enabled or not.
FIPS also mandates using /dev/random instead of /dev/urandom.

Assignee: nobody → msirringhaus
Severity: -- → S4
Priority: -- → P3

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:msirringhaus, could you have a look please?
For more information, please visit auto_nag documentation.

Flags: needinfo?(msirringhaus)
Flags: needinfo?(gpascutto)
Flags: needinfo?(gpascutto)
Pushed by gpascutto@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a15a51cdc10b
Expose /dev/random and /proc/sys/crypto/fips_enabled in sandboxes. r=bryce,gcp
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 96 Branch
Flags: needinfo?(msirringhaus)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: