0
Files
src/sandbox
Nico Weber 0571795076 Remove std::vector<const T>s in sandbox/
We can make the vector itself const and not lose any guarantees.

No behavior change.

Bug: 323708866
Change-Id: Icae5232e2ba6b9ff63d21e07a6767ae120c9a776
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5273483
Reviewed-by: Alex Gough <ajgo@chromium.org>
Auto-Submit: Nico Weber <thakis@chromium.org>
Commit-Queue: Alex Gough <ajgo@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1257015}
2024-02-06 21:43:13 +00:00
..
2024-01-23 22:04:11 +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.