commit | ef0d21c3e396e2928f4ad5798f309f4995d1a161 | [log] [tgz] |
---|---|---|
author | Avi Drissman <avi@chromium.org> | Mon Jan 10 18:48:18 2022 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Jan 10 19:00:32 2022 |
tree | 5a30ef51f22c1d66274513853cf9c0e04c375d2e | |
parent | d7182755795e01c01b270f4f45626fd62e390fb1 [diff] |
Use std::ignore rather than ignore_result in sandbox/ Bug: 1285085 Change-Id: I67ce4e94fc7a10c61385d412a13034966bc87cf4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3374334 Auto-Submit: Avi Drissman <avi@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/main@{#957121} NOKEYCHECK=True GitOrigin-RevId: 07184f54056e4cfcf11c4a8e81b9370cc06e559c
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.