commit | a2b408fc6673679c0b9b0a75ac2433261cc5f77b | [log] [tgz] |
---|---|---|
author | Will Harris <wfh@chromium.org> | Wed Dec 08 22:40:14 2021 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Dec 08 22:56:15 2021 |
tree | 1a22287eaf135565b7def6320984da29f977290b | |
parent | 67127c651d5484252c58fd54d0593b9d0ec5837b [diff] |
Add ERROR log message for sandbox file system permissions issues. This will be needed to be visible to downstream to be able to diagnose configuration issues when the network service sandbox is enabled. BUG=841001 Change-Id: I4286905c6a5ff84555932c72406e589669cea44c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3323848 Reviewed-by: James Forshaw <forshaw@chromium.org> Commit-Queue: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/main@{#949765} NOKEYCHECK=True GitOrigin-RevId: 3b7323e55a734d03f135ea1fe86264d32263ea2e
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.