commit | 222e0469827c093ae55d0d4115aca364e9e5afd4 | [log] [tgz] |
---|---|---|
author | Lei Zhang <thestig@chromium.org> | Tue Aug 17 17:44:09 2021 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Aug 17 18:10:35 2021 |
tree | 954816a7a10f1f77dc3c576800dd94dfc3fa9d5b | |
parent | a23297d4a26265cae6ab47d88c6948f504beb582 [diff] |
Mac: Let Print Compositor processes access SystemAppearance.bundle. In some cases, while print compositing, Core Text wants to know about the application's appearance. Set the sandbox policies to allow this. Bug: 1237384 Change-Id: I216605a8967027566bf442bcf76a9ea55759d093 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3099245 Commit-Queue: Lei Zhang <thestig@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#912637} NOKEYCHECK=True GitOrigin-RevId: b13e7323790d1a6f176c1d4953f0023ae0d2c154
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.