chromium/src
0
Fork 0
Code Activity

docs: remove reference to linux_sandbox_path GYP variable

Browse Source 
It has been gone and code does not look for it anymore.

BUG=None

Change-Id: Ia1dbee151490082d3d61aa1f9c39154b000bf6d8
Reviewed-on: https://chromium-review.googlesource.com/509612
Reviewed-by: Richard Coles <torne@chromium.org>
Commit-Queue: Thiago Farina <tfarina@chromium.org>
Cr-Commit-Position: refs/heads/master@{#473578}
This commit is contained in:
Thiago Farina
2017-05-20 18:47:46 -03:00
committed by Commit Bot
parent 9404a23e00
commit de2cf8e85d
1 changed files with 3 additions and 8 deletions

11
docs/linux_suid_sandbox.md

@ -11,14 +11,9 @@ renderers using a `SUID` helper binary. This is one of
## `SUID` helper executable
The `SUID` helper binary is called `chrome_sandbox` and you must build it
separately from the main 'chrome' target. To use this sandbox, you have to
specify its path in the `linux_sandbox_path` GYP variable. When spawning the
[zygote process](linux_zygote.md), if the `SUID` sandbox is enabled, Chromium
will check for the sandbox binary at the location specified by
`linux_sandbox_path`. For Google Chrome, this is set to
`/opt/google/chrome/chrome-sandbox`, and early version had this value hard coded
in `chrome/browser/zygote_host_linux.cc`.
separately from the main 'chrome' target. Chrome now just assumes it's next
to the executable in the same directory. You can also control its path
by CHROME_DEVEL_SANDBOX environment variable.
In order for the sandbox to be used, the following conditions must be met: