| commit | b13d5ba2b1edabd7808cbb10a4d4430f04d8bae0 | [log] [tgz] |
|---|---|---|
| author | Peter Kasting <pkasting@chromium.org> | Thu Jul 14 18:43:19 2022 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jul 14 18:53:16 2022 |
| tree | 7ad2e4dc7bb0f3b7d8251a1fbe455c01d73a79f2 | |
| parent | f49634bd34e7be5a3e8a96f1d0b43e6051d8d94e [diff] |
Reland "Prevent unsafe narrowing: base/ for Linux part 2 of n" Bug: 1292951 Change-Id: I2ba0e069a26ebac13dcd4ae162764d28d90f4a73 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3758876 Reviewed-by: danakj <danakj@chromium.org> Owners-Override: danakj <danakj@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/main@{#1024348} NOKEYCHECK=True GitOrigin-RevId: a0b914dcebb6bf420b2d73dd3977051b3fac20d2
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.