commit | 62d2a60709a841eba0cba9d219cb6c3fdfc421c3 | [log] [tgz] |
---|---|---|
author | Avi Drissman <avi@chromium.org> | Wed Jul 29 16:05:22 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Jul 29 16:05:22 2020 |
tree | 66e5923aa42ef653cd4feaf3167bbd877f87e1ef | |
parent | a9e76f5ea50434b3ff171eb52b0277204e2d9a85 [diff] |
Migrate to OS_MAC and OS_APPLE in sandbox Bug: 1105907 Change-Id: Ic29ebc9a008b0ef4ac64a639150ed99b62222988 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2325094 Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#792718} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: fdadd6a800f864080f1991688e4f8e24536b47b6
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.