0
Files
src/sandbox
Alex Gough a644de6369 Remove WinSboxAllowSystemFonts escape valve
This has been in Stable for a whole milestone so we can remove the
emergency off switch.

Bug: 1023583
Change-Id: I39f921c5816ed5eae64c40b40cf15b202e24191e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4752719
Commit-Queue: Alex Gough <ajgo@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1179852}
2023-08-04 21:59:16 +00:00
..
2023-08-03 17:42:53 +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.