0
Files
src/sandbox
Will Harris 1dc8d49885 Do not attempt to set App Container ACLs on non-Windows.
This is needed for when doing a cross-compile of a Windows build
and there is never any need to set ACLs.

BUG=1212742

Change-Id: I54f7d26b260c7949c8de5bda7e908dfd213d6f08
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2935817
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Will Harris <wfh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#889421}
2021-06-04 20:06:25 +00:00
..
2021-03-31 22:00:52 +00:00
2021-04-06 21:53:09 +00:00

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.