0
Files
src/sandbox
Tom Sepez 978847c229 Suppress still another batch of -Wunsafe-buffers-in-libc-calls warnings.
These are mainly win-specific files this time around.

Bug: 390223051
Change-Id: I07b378500b76896ddb28cf52d4ad2d2d77d0b7f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6369920
Reviewed-by: Alex Gough <ajgo@chromium.org>
Commit-Queue: Tom Sepez <tsepez@chromium.org>
Owners-Override: Alex Gough <ajgo@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1436413}
2025-03-21 20:43:59 -07: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.