657d3ce7b0
Some of the logging in SandboxBPF::DisableIBSpec() is causing debug-build test failures because the sandbox test code expects no output for many tests. This CL removes an unnecessary LOG(INFO) and changes one to a VLOG(1). Bug: 1171027, 1206746 Change-Id: I8e255805e7aa53033205a28231ee366e03069edf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2880845 Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Matthew Denton <mpdenton@chromium.org> Cr-Commit-Position: refs/heads/master@{#881297}
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.