commit | d1d97f3d31bbd059d6d517cfd1e298129de7bbbf | [log] [tgz] |
---|---|---|
author | Alan Screen <awscreen@chromium.org> | Tue Sep 14 22:19:21 2021 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Sep 14 22:30:33 2021 |
tree | a40583106da4b3b2c104a6ada179b8b426dc8479 | |
parent | 69b167b23fb4a83d47fb196f16dd8627c6a4042b [diff] |
Use build flag for OOP printing As out-of-process printing support gets filled in there is an increasing number of places which require compile-time conditioning for the feature implementation. It is more concise and clear if these code blocks are enclosed by a build flag, rather than to continue repeating the condition based upon the list of Windows, macOS, Linux, and ChromeOS platforms which this feature is currently supported on. Bug: 809738 Change-Id: I5b9bda291c3daf15b44b9e4ab699cda7eafcf99f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3154758 Reviewed-by: Lei Zhang <thestig@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Reviewed-by: Erik Chen <erikchen@chromium.org> Commit-Queue: Alan Screen <awscreen@chromium.org> Cr-Commit-Position: refs/heads/main@{#921439} NOKEYCHECK=True GitOrigin-RevId: d8170454da4cdaab0a8ced84476fcd3857ccaf36
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.