commit | 594a5a4ccedb474ea8ca23dbbeb86faba0168e58 | [log] [tgz] |
---|---|---|
author | Keishi Hattori <keishi@chromium.org> | Mon May 02 13:09:31 2022 |
committer | Copybara-Service <copybara-worker@google.com> | Mon May 02 13:25:19 2022 |
tree | fd5e6a88ed5d47253774984632e0005211dd2188 | |
parent | ce612770d938e564d8b741030389e716488c1c0d [diff] |
Add RAW_PTR_EXCLUSION annotations to fields Bug: 1273182 Change-Id: I235ab43fc32e2a313197a4b535a93991581dcdfa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3607476 Owners-Override: Keishi Hattori <keishi@chromium.org> Reviewed-by: Ćukasz Anforowicz <lukasza@chromium.org> Commit-Queue: Keishi Hattori <keishi@chromium.org> Reviewed-by: Bartek Nowierski <bartekn@chromium.org> Cr-Commit-Position: refs/heads/main@{#998328} NOKEYCHECK=True GitOrigin-RevId: 488b760ceb55d72daaa0823e45a8b07d61be32f6
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.