commit | 07874d89a4a7b40f43cca398398121c8af28fc68 | [log] [tgz] |
---|---|---|
author | David Dorwin <ddorwin@chromium.org> | Fri Nov 19 20:03:40 2021 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Nov 19 20:22:18 2021 |
tree | b8aa381d681e9d29fd79594d4cedb52933f482f3 | |
parent | bee0ab3710fd565ea08afdb1b962c8723e8e1cd6 [diff] |
[fuchsia] Fix comment related to ZX_POL_AMBIENT_MARK_VMO_EXEC Bug: 1106561 Change-Id: I5f66ff86030a027e8b22283cf9285fd32b77b7f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3292374 Auto-Submit: David Dorwin <ddorwin@chromium.org> Reviewed-by: Kevin Marshall <kmarshall@chromium.org> Reviewed-by: Alex Gough <ajgo@chromium.org> Commit-Queue: Alex Gough <ajgo@chromium.org> Cr-Commit-Position: refs/heads/main@{#943620} NOKEYCHECK=True GitOrigin-RevId: 30a5321a90c5231526eb428dbe4dbfa7737e5240
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.