commit | 3781d3bcada731ed82a36c6c5063cbf406ce1aeb | [log] [tgz] |
---|---|---|
author | Alex Gough <ajgo@chromium.org> | Wed Aug 18 20:07:30 2021 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Aug 18 20:23:35 2021 |
tree | ce0c30bf9b8371f2e1a126a206c3e853ea5433bd | |
parent | b201d93c8f4bd674df90809d8d53c2c1eb9a29ce [diff] |
Specify cast mirroring service sandbox in mojom This moves to using the ServiceSandbox mojom attribute to select the sandbox, and removes reference from service_sandbox_type.h No functional changes, see linked bug for details. Bug: 1210301 Change-Id: Ia49349d3949ff841072cf76c30604ba6398b7adb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3094480 Commit-Queue: Alex Gough <ajgo@chromium.org> Reviewed-by: Jordan Bayles <jophba@chromium.org> Reviewed-by: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/master@{#913122} NOKEYCHECK=True GitOrigin-RevId: 25c60b180996a68f9c644e8d24e3c2b924fa6da9
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.