6a5265cab1
This code needs to pass threads to children. Rather than allowing all thread handles this CL instead bypasses the hook in process_thread_dispatcher.cc directly. This means that other Chrome code accidentally sending thread handles to children should still be caught by the checks. Bug: 40408399 Change-Id: Ide865ac3b42ef4ee3bd8272af7e9ac2f88d9ac41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6127931 Commit-Queue: Alex Gough <ajgo@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Cr-Commit-Position: refs/heads/main@{#1401013}
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.