6200bc3bf8
Moves the variable backing 'EnableCsrssLockdown' to sandbox/policy/features.h and exposes it on chrome://sandbox. The variable is also renamed to remove the redundant 'Feature' suffix. The feature's exposed name is not changed so fieldtrials and commandlines using it are not affected. Bug: 40408399 Change-Id: I94cb8d8802e81ceaef0369c35c1bcc633d9fcf17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6091995 Auto-Submit: Alex Gough <ajgo@chromium.org> Reviewed-by: Will Harris <wfh@chromium.org> Commit-Queue: Alex Gough <ajgo@chromium.org> Cr-Commit-Position: refs/heads/main@{#1395801}
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.