b6b8784e6d
Lacros is gone. - Replace any IS_CHROMEOS_ASH uses with IS_CHROMEOS. - Replace any is_chromeos uses with is_chromeos. - Remove any IS_CHROMEOS_LACROS uses and associated code. - Remove any is_chromeos_lacros uses. - Where appropriate, remove includes of build/chromeos_buildflags.h or replace with build/build_config.h. - Remove any imports of build/config/chromeos/ui_mode.gni. Bug: b:354842935 Change-Id: Iddd81988fa3f47988528124eef82b69497821f45 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6242475 Auto-Submit: Georg Neis <neis@chromium.org> Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org> Cr-Commit-Position: refs/heads/main@{#1417996}
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.