52fa5a7f26
To continue the migration away from TaskRunnerHandles, the codebase was refactored using the following scripts: shell script: https://paste.googleplex.com/4673967729147904 python: https://paste.googleplex.com/5302682490241024 This will do a few sed-like modifications, changing calls to methods of SequencedTaskRunnerHandle to calls to methods of SequencedTaskRunner::CurrentDefaultHandle, and swapping includes. Bug: 1026641 AX-Relnotes: n/a. Change-Id: I49e50a2bd1e78b00e7c067219fff96d2e0bc0b46 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3983373 Commit-Queue: Gabriel Charette <gab@chromium.org> Owners-Override: Gabriel Charette <gab@chromium.org> Reviewed-by: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/main@{#1071032}
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.