
Previously, CL 2935817 landed a check for the main sandbox target but not for the test target that also depends on having correct filesystem ACLs. This CL also adds the conditional dependency for that target fixing this issue Once And For All. BUG=1212742 Change-Id: I42b9810818f10a3dcbd43ee7429ddfef43beae07 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2982844 Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/master@{#895401}
Sandbox Library
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.