202
edits
Security/Sandbox/Deny Filesystem Access: Difference between revisions
Security/Sandbox/Deny Filesystem Access (view source)
Revision as of 17:39, 19 July 2016
, 19 July 2016→Cross-Platform Blockers
Haftandilian (talk | contribs) (Cross-Platform Blockers) |
Haftandilian (talk | contribs) |
||
| Line 39: | Line 39: | ||
| {{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 || | | {{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 || | ||
# For print-to-file (e.g., PDF, postscript). | # For print-to-file (e.g., PDF, postscript). | ||
# | # Printing to a printer seems to work with write access to $HOME disabled. Without using print_via_parent, using dtrace I saw plugin-container read from ~/.cups/client.conf and write to the content process temp dir ~/Library/Caches/TemporaryItems/Temp-{UUID}. | ||
|- | |- | ||
| {{bug|1136836}} Load chrome: URLs through parent process || Blocks disabling read access to parts of the profile dir || | | {{bug|1136836}} Load chrome: URLs through parent process || Blocks disabling read access to parts of the profile dir || | ||