| commit | 917fd162313c50d2d67edb689839ed7d03a7d1fb | [log] [tgz] |
|---|---|---|
| author | Stephen Boyd <swboyd@chromium.org> | Thu Feb 03 20:11:20 2022 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Feb 03 20:28:09 2022 |
| tree | a793ae09add5e855a7c211c4bde53deb6bf19d51 | |
| parent | 135b4923d4eb1f70afca42a04d189b53929f6a9b [diff] |
Fix build on arm64-asan There's no __NR_pipe define on aarch64, but there is __NR_pipe2 so use that if aarch64 architecture is targeted. Bug: b:172702178 Change-Id: Id58d54627c90ac3b07044d0f635d3bc90e3f6af6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3434102 Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Stephen Boyd <swboyd@chromium.org> Cr-Commit-Position: refs/heads/main@{#966877} NOKEYCHECK=True GitOrigin-RevId: b2cebb2293a5b1b065fa4d8af067fa58123a33f6
This directory contains platform-specific sandboxing libraries. Sandboxing is a technique that can improve the security of an application by separating untrustworthy code (or code that handles untrustworthy data) and restricting its privileges and capabilities.
Each platform relies on the operating system's process primitive to isolate code into distinct security principals, and platform-specific technologies are used to implement the privilege reduction. At a high-level:
mac/ uses the Seatbelt sandbox. See the detailed design for more.linux/ uses namespaces and Seccomp-BPF. See the detailed design for more.win/ uses a combination of restricted tokens, distinct job objects, alternate desktops, and integrity levels. See the detailed design for more.Built on top of the low-level sandboxing library is the //sandbox/policy component, which provides concrete policies and helper utilities for sandboxing specific Chromium processes and services. The core sandbox library cannot depend on the policy component.