|
|
| Line 9: |
Line 9: |
| ! Platform !! Current Status of Content Filesystem Sandboxing on Nightly | | ! Platform !! Current Status of Content Filesystem Sandboxing on Nightly |
| |- | | |- |
| | Windows || | | | Windows/Mac/Linux || |
| Level 1: Low integrity restricts write access
| | Read/write access restrictions is now shipping on all platforms. For more details see https://wiki.mozilla.org/Security/Sandbox#Current_Status |
| Level 2: Adds restrictions to read access
| |
| |-
| |
| | OS X || Some directories are read/write protected, but this will not provide real security until the bulk of the $HOME directory is read/write protected.
| |
| | |
| On OS X, the Firefox Profile directory is stored within ~/Library/Application Support/Firefox/Profiles/. ~/Library is read/write protected with a few exceptions for some specific subdirectories. Access to $HOME and other areas of the filesystem is not restricted. i.e., the content process can read and write to/from anywhere the OS permits: $HOME and temporary directories. The ~/Library read/write prevention could be bypassed because the rest of the $HOME is read/write accessible. For example, a compromised process could add malicious commands to ~/.login-type files to copy data from ~/Library when a user logs in.
| |
| |-
| |
| | Linux ||
| |
| Level 2: Read allowed. Write allowed in /dev/shm and /tmp (TMPDIR).
| |
| |} | | |} |
|
| |
|