| commit | 20a9a3ad484caea1f97b9c8824a79a5c8bf8a958 | |
| author | hidehiko <hidehiko@chromium.org> | |
| Thu, 11 Dec 2014 03:51:21 +0000 (10 19:51 -0800) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Thu, 11 Dec 2014 03:51:53 +0000 (11 03:51 +0000) | ||
| tree | ee76cbf4896ba04a36c559962f6b8d51dc11f86c | treesnapshot (tar.gz zip) |
| parent | 2ff1341a5b3dc65806b7c6b294240a3f05fe8a81 | commitdiff |
Non-SFI mode: Use dummy PID for NaCl's IPC channel and IPC channel on Linux platform.
We do not want to expose PID from process on Linux, because it does not play any security role.
Specifically, in NaCl processes, now although getpid() syscall is prohibited by seccomp sandbox, it looks working, probably because of the cache in libc layer.
By this CL, Linux IPC, including nacl_helper_nonsfi, uses dummy PID (-1).
Note; as for nacl_helper process, currently, the process is under PID namespace, so "dummy-like-" PID is already used.
BUG=358465
TEST=Ran trybot.
Review URL: https://codereview.chromium.org/695353005
Cr-Commit-Position: refs/heads/master@{#307853}
We do not want to expose PID from process on Linux, because it does not play any security role.
Specifically, in NaCl processes, now although getpid() syscall is prohibited by seccomp sandbox, it looks working, probably because of the cache in libc layer.
By this CL, Linux IPC, including nacl_helper_nonsfi, uses dummy PID (-1).
Note; as for nacl_helper process, currently, the process is under PID namespace, so "dummy-like-" PID is already used.
BUG=358465
TEST=Ran trybot.
Review URL: https://codereview.chromium.org/695353005
Cr-Commit-Position: refs/heads/master@{#307853}