| commit | bf2eedb38b1cf2a5ce8e73aa976cb323a9e4f1ae | [log] [tgz] |
|---|---|---|
| author | James Forshaw <forshaw@chromium.org> | Fri Nov 12 00:41:20 2021 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Nov 12 00:52:29 2021 |
| tree | 01bef05a56248d98b200b8c117750ccc0ec42f5c | |
| parent | 1de8cfdb47a4c3b495c0a26a95aca4b866e83df8 [diff] |
[Windows] Remove old sandbox Sid class. This CL removes the old sandbox Sid class and moves all users to the new class in base. Bug: 1266853 Change-Id: I572027bd5e846f71e8caa5849401fdef895d56f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3273701 Commit-Queue: James Forshaw <forshaw@chromium.org> Reviewed-by: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/main@{#941001} NOKEYCHECK=True GitOrigin-RevId: 44f1184597a11b68b7658b5c2fb6d783b50b5590
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.