6d18fd4823
kMaxServiceCount is needlessly larger than it needs to be and can be directly coupled to the number of IPCs supported. This CL renames it to kSandboxIpcCount and defines it by reference to the IpcTag enum. (History: kMaxServiceCount was last increased in https://codereview.chromium.org/1856993003.) Bug: 336349858 Change-Id: Idcc690c22667649faa5614b36d595e12f59e1b34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5491721 Reviewed-by: Will Harris <wfh@chromium.org> Commit-Queue: Alex Gough <ajgo@chromium.org> Cr-Commit-Position: refs/heads/main@{#1294191}
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.