0
Files
src/sandbox
Matthew Dalzell ffd60d248d sandbox: allow PROT_BTI, PROT_MTE madvise flags for Arm
Bug: 1211510, 1145581, 1137393
Change-Id: I9b4a2c94293bf1373370096fe435da6766d48c47
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3016488
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Richard Townsend <richard.townsend@arm.com>
Cr-Commit-Position: refs/heads/master@{#900186}
2021-07-09 22:48: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.