| commit | 96d2a85e1e85a1a5c188c52bbd586f4b167172bd | [log] [tgz] |
|---|---|---|
| author | David Dorwin <ddorwin@chromium.org> | Thu Nov 04 17:56:12 2021 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Nov 04 18:18:26 2021 |
| tree | 7762c5f28870e3bed2b705d433643936709142e2 | |
| parent | d5c77910b9466a41343b8f0c4ebaa7a75a9aaccc [diff] |
Replace inappropriate uses of DIR_ASSETS Convert test code accessing test data to DIR_GEN_TEST_DATA_ROOT or DIR_SRC_TEST_DATA_ROOT as appropriate. Convert one Fuchsia-specific use to the literal it intends to use. Also document some uses of DIR_GEN_TEST_DATA_ROOT added in crrev.com/c/3237884. Bug: 1262430 Change-Id: I3e32495ef4d49f98b3e58971cd30990be427e698 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3254176 Auto-Submit: David Dorwin <ddorwin@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Ken Rockot <rockot@google.com> Reviewed-by: Fabrice de Gans <fdegans@chromium.org> Reviewed-by: Andrey Kosyakov <caseq@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Xiaohan Wang <xhwang@chromium.org> Commit-Queue: David Dorwin <ddorwin@chromium.org> Cr-Commit-Position: refs/heads/main@{#938352} NOKEYCHECK=True GitOrigin-RevId: 95fefdd6c41d7d3736dd861332f2f4feb6e4dc7e
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.