| commit | 0768a3c3d8b734a34baf830f4fec09510e01d335 | [log] [tgz] |
|---|---|---|
| author | Alex Gough <ajgo@chromium.org> | Thu Dec 02 08:48:42 2021 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Dec 02 09:00:09 2021 |
| tree | 855a75bf66d6aa6bcbb31b608e63b46cc24e4d24 | |
| parent | 9095e15ed82a3ed4a20bf0e24e3da3c796cf4dab [diff] |
Change description of unmodified token in chrome://sandbox to None Change-Id: I487616cf005711e81081c574fcf384fc990bab10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3312560 Auto-Submit: Alex Gough <ajgo@chromium.org> Reviewed-by: Will Harris <wfh@chromium.org> Commit-Queue: Alex Gough <ajgo@chromium.org> Cr-Commit-Position: refs/heads/main@{#947405} NOKEYCHECK=True GitOrigin-RevId: b4aee97b1886313967ad9c9859a04d3654bc7030
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.