0
Files
src/sandbox
James Forshaw 2a533854c8 [Windows] Remove unused ResolveRegistryName utility.
This CL removes an unused utility method from the sandbox during more
general cleanup of the sandbox policy and utility code.

Bug: 339497724
Change-Id: I847be8712b118f484d1372456790d243f803e56b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5547792
Reviewed-by: Alex Gough <ajgo@chromium.org>
Commit-Queue: James Forshaw <forshaw@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1305087}
2024-05-23 15:10:34 +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.