5b36b82e2d
This CL is to replace lpacAppServices with lpacInstrumentation for SandboxType::kMediaFoundationCdm. https://chromium-review.googlesource.com/c/chromium/src/+/2401506 has a mistake of using lpacAppServices. Windows Media Foundation needs lpacInstrumentation capability to access Windows Event Tracings and Telemetries. Bug: 999747 Change-Id: I68ba48b531dd9bb611db08073017a9bf562605f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2462729 Reviewed-by: Will Harris <wfh@chromium.org> Commit-Queue: Frank Li <frankli@microsoft.com> Cr-Commit-Position: refs/heads/master@{#816323}
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.