b3fb42320c
Introduce a wrapper class (similar to base::StrongAlias) for PlatformThreadId, whose API assumes that the value can be 64-bit. It forces explicit conversion to integers with various bitness, and makes conversion to 32-bit be explicit about truncation. The values are currently all still 32-bit -- follow-up work will make thread id values on macOS 64-bit. Bug: 40187449 Change-Id: Ic635c346be1c3a0d62fd573572f4fcdc642a734f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6206469 Reviewed-by: Peter McNeeley <petermcneeley@google.com> Reviewed-by: Mark Mentovai <mark@chromium.org> Owners-Override: Mark Mentovai <mark@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Victor Vianna <victorvianna@google.com> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Mikhail Khokhlov <khokhlov@google.com> Reviewed-by: Ahmed Fakhry <afakhry@chromium.org> Cr-Commit-Position: refs/heads/main@{#1416712}
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.