0
Files
src/sandbox
Oksana Zhuravlova b2721bfd07 [CodeHealth] Add a reason for RAW_PTR_EXCLUSION in sandbox_nt_util.h
The memory might be managed by the OS and not PartitionAlloc.

Bug: 346693833
Change-Id: I122f502e9a60cc6ad0f8be13bc94e67d22a92437
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6298505
Reviewed-by: Alex Gough <ajgo@chromium.org>
Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1429030}
2025-03-06 10:36:55 -08: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.