202
edits
Security/Sandbox/Deny Filesystem Access: Difference between revisions
Security/Sandbox/Deny Filesystem Access (view source)
Revision as of 23:34, 16 May 2016
, 16 May 2016→Cross-Platform Blockers
Haftandilian (talk | contribs) |
Haftandilian (talk | contribs) |
||
| Line 30: | Line 30: | ||
| {{bug|1090454}} Trigger print jobs from the parent instead of the child when printing from a remote browser || Blocks disabling write access to $HOME and other locations || TBD. For printing and print-to-file. (TBD, because I don't understand the details of why printing requires writing to filesystem). | | {{bug|1090454}} Trigger print jobs from the parent instead of the child when printing from a remote browser || Blocks disabling write access to $HOME and other locations || TBD. For printing and print-to-file. (TBD, because I don't understand the details of why printing requires writing to filesystem). | ||
|- | |- | ||
| {{bug|1136836}} Load chrome: URLs through parent process || Blocks disabling read access to $HOME || Addons can load scripts and resources from the profile directory using chrome: and resource: URL's. | | {{bug|1136836}} Load chrome: URLs through parent process || Blocks disabling read access to $HOME || Addons can load scripts and resources from the profile directory using chrome:// and resource:// URL's. An add-on calling loadFromScript("chrome://foo/bar") from the Parent process results in Content trying to load that URL. | ||
|- | |||
| {{bug|1109293}} Desktop content process resource:// and moz-extension:// URIs should not directly use file:/// || TBD || TBD | |||
|} | |} | ||