
This CL is part of the wider spanification / arrayification effort [1] and does not (intentionally) introduce behavioral change. It applies the `std::array` rewrite to sandbox as close as possible to the output directly written by `spanify`, with no hand-rolled fixes (except where rebasing would require). This change (and its siblings taken together) is thought not to cause any measurable perf regressions [2]. [1] https://issues.chromium.org/356643982 [2] https://docs.google.com/document/d/1jughaR6JKn7T-dDjMou10awyNkhE5T-vLY_K2YMqHE4/edit?tab=t.0#heading=h.r2eguxl5lhu7 This CL was uploaded by an experimental version of git cl split (https://crbug.com/389069356). Bug: 406029216 Change-Id: I7272cf68f36effff56dce9a130a4d5364cae1174 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6433380 Commit-Queue: Kalvin Lee <kdlee@chromium.org> Auto-Submit: Kalvin Lee <kdlee@chromium.org> Reviewed-by: Matthew Denton <mpdenton@chromium.org> Cr-Commit-Position: refs/heads/main@{#1443903}
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.