fd7a14c53b
This NOTREACHED() is not actionable and results when shutdown is taking too long - collecting a crash here takes up more system resources. Instead, TerminateProcess() with a new exit code which should show up in Stability.BrowserExitCodes. Bug: 360764659 Change-Id: I1c769b519e4972fbf2f13bead89c7faf9c1bdfa0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5908492 Reviewed-by: David Pennington <dpenning@chromium.org> Reviewed-by: Mark Pearson <mpearson@chromium.org> Commit-Queue: Alex Gough <ajgo@chromium.org> Cr-Commit-Position: refs/heads/main@{#1365936}
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.