| commit | dab9b70f37bcc9ab788c41407980244eeb11be3b | [log] [tgz] |
|---|---|---|
| author | James Forshaw <forshaw@chromium.org> | Thu Dec 09 16:39:31 2021 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Dec 09 16:56:12 2021 |
| tree | cb84d301698b6526b4f8cfe5e5cbe786e12cc4c9 | |
| parent | bcd054640db354f9e6e11782b587789c3efd641a [diff] |
[Windows] Remove old sandbox build files. This CL removes the old unused Visual Studio project files. These have not been modified in at least 10 years, they're vastly out of date and are designed for VS2005. Bug: 1270309 Change-Id: I793440764944fc18ed688ea02a294441f2ff1c54 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3324372 Reviewed-by: Will Harris <wfh@chromium.org> Commit-Queue: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/main@{#950104} NOKEYCHECK=True GitOrigin-RevId: 4d0f15234272ba7cd6869cd79c3baaf9c9f2ad21
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.