commit | 3b922c3ef3cc6d62e9b334f39baf52bbfadb51a5 | [log] [tgz] |
---|---|---|
author | Nico Weber <thakis@chromium.org> | Mon Aug 16 17:16:24 2021 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Aug 16 17:30:24 2021 |
tree | 6897830e874ac5771df62628666ccf4680ce2a84 | |
parent | 42bcb37df0453fda0bae32cfdc9f7af5bb18b712 [diff] |
Fix some -Wunreachable-code-aggressive warnings Bug: 1066980 Change-Id: Ia1987f4c87af4e574a91e06503a0e8fba5d0d87c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3095231 Auto-Submit: Nico Weber <thakis@chromium.org> Commit-Queue: Robert Sesek <rsesek@chromium.org> Owners-Override: Nico Weber <thakis@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#912224} NOKEYCHECK=True GitOrigin-RevId: 2771b0fedf0c9f42d16523c155d916292a38f68b
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.