43b37ba87e
Some SandboxBPF.* tests continuously shows test failures, which is caused because UBSan shows alerts, and breaks the condition. This CL exclude UBSan until an underlying issue has been fixed. Bug: 375489584 Change-Id: Ia5a5934c718bbc6d37dc97190c3426bb22b6ee38 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5960925 Auto-Submit: Yoshisato Yanagisawa <yyanagisawa@chromium.org> Reviewed-by: Nico Weber <thakis@chromium.org> Reviewed-by: Matthew Denton <mpdenton@chromium.org> Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org> Cr-Commit-Position: refs/heads/main@{#1373748}
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.