commit | 84b0588dd89c02f7445f64a034169bd452f6c5f0 | [log] [tgz] |
---|---|---|
author | Robert Sesek <rsesek@chromium.org> | Tue Sep 07 16:52:58 2021 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Sep 07 17:08:45 2021 |
tree | aa07a2ef41b7ae1c0fe3526da720a5ce2ea0d613 | |
parent | f93119b7c5787e2773ec9febe8ce9895c75498a5 [diff] |
mac: Add SeatbeltExtension::FILE_READ_WRITE This permits granting a process read/write access to a directory path, under which it can read, write, and create new files after the sandbox is initialized. Bug: 1245798 Change-Id: I64c1d697bf20cf7b4e5a1cfa5af0df56ad97cf08 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3126340 Reviewed-by: Greg Kerr <kerrnel@chromium.org> Commit-Queue: Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/main@{#918828} NOKEYCHECK=True GitOrigin-RevId: 30f69f27dc24109a50cf58d8038ad0e1a42f5dc7
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.