| commit | bee0ab3710fd565ea08afdb1b962c8723e8e1cd6 | [log] [tgz] |
|---|---|---|
| author | James Forshaw <forshaw@chromium.org> | Fri Nov 19 17:31:35 2021 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Nov 19 17:44:29 2021 |
| tree | 68f017006aab1fd9291519b55525cc90e88f9181 | |
| parent | 1ba4e4bc1b081e61382372260dcc4b742124f114 [diff] |
[Windows] Remove SUBSYS_SYNC sandbox policy. This CL removes the SUBSYS_SYNC sandbox policy and associated tests. Bug: 1058631 Change-Id: I52d3dae13fee3635543254e192a48f9db4a218c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3292504 Commit-Queue: James Forshaw <forshaw@chromium.org> Reviewed-by: Alex Gough <ajgo@chromium.org> Cr-Commit-Position: refs/heads/main@{#943580} NOKEYCHECK=True GitOrigin-RevId: eb91315e91f0a1eb6b4ea0da6a5647dcd21acb93
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.