| commit | a28dee4bb44ad56a3d11df02af6c2ea0d2e66037 | [log] [tgz] |
|---|---|---|
| author | Hans Wennborg <hans@chromium.org> | Wed Sep 08 17:17:35 2021 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Sep 08 17:36:09 2021 |
| tree | 6978b00c9ffbdf3d95b455d073763a17edfb3aba | |
| parent | c3d7127bc014805330aa6279fbeec52d4a8202f3 [diff] |
Disable vfork()-style clone() in ChrootToSafeEmptyDir() for MSan This code doesn't work with recent versions of MSan, see bug. Bug: 1247458 Change-Id: Ic7ffdfc7db3ce06b00d0162f4b9f656d791674e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3148493 Reviewed-by: Nico Weber <thakis@chromium.org> Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Commit-Queue: Hans Wennborg <hans@chromium.org> Cr-Commit-Position: refs/heads/main@{#919308} NOKEYCHECK=True GitOrigin-RevId: ef528cedb5fb3b346c08b39bda80c5555f98ed36
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.