| commit | a309c97ab4cbfc983b20f7bd4b2f7eb08728e671 | [log] [tgz] |
|---|---|---|
| author | Robert Sesek <rsesek@chromium.org> | Fri Nov 19 02:34:36 2021 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Nov 19 02:56:19 2021 |
| tree | eca4b4fa11f5d1a2cf5f487e7939a7a6d5287a76 | |
| parent | d1201d6fa2cd7acc81b8c2841f197f587dd58b36 [diff] |
android: Possibly block at runtime sched_setaffinity and sched_getaffinity These are only used by ongoing experiments, and they should be blocked if not in the experiment group. Bug: 1271302 Change-Id: Ic8a23bb691857de51a5683dfafd4f802627a2e15 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3290227 Reviewed-by: John Abd-El-Malek <jam@chromium.org> Reviewed-by: Eric Seckler <eseckler@chromium.org> Reviewed-by: Matthew Denton <mpdenton@chromium.org> Commit-Queue: Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/main@{#943394} NOKEYCHECK=True GitOrigin-RevId: 1a0498917c56c7155010a309629304dc0bfc3676
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.