commit | ec0263b4c3028a61102e487828afdf4009ba0923 | [log] [tgz] |
---|---|---|
author | Alex Gough <ajgo@chromium.org> | Wed Aug 11 01:23:47 2021 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Aug 11 01:37:54 2021 |
tree | 53bc3645c4b1c978cf609e0e487964a92b28b7dc | |
parent | 7aa9146a60dcf31a8d557f312ccf06943b30d8df [diff] |
Specify CDM sandboxes in mojom This moves to using the ServiceSandbox mojom attribute to select the sandbox, and removes reference from service_sandbox_type.h. Some mojo includes are moved to .mojom-forward.h where sensible. No functional changes, see linked bug for details. Bug: 1210301 Change-Id: I741043f1e57ae10ea65fca32a4c97421d4e9e7d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3083167 Commit-Queue: Alex Gough <ajgo@chromium.org> Reviewed-by: Will Harris <wfh@chromium.org> Reviewed-by: Xiaohan Wang <xhwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#910618} NOKEYCHECK=True GitOrigin-RevId: 048e91e6fd6de2d610713b948f8a57166c9c356f
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.