commit | 8541c3754a163807cc303ac510da05bec54951ef | [log] [tgz] |
---|---|---|
author | Alessandro Astone <ales.astone@gmail.com> | Mon Feb 28 15:50:43 2022 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Feb 28 16:06:24 2022 |
tree | d7cffa249464e90f009800ea56b0034de3aafbd8 | |
parent | 6142185119071b415d4e18f31ee0ffbbec41a6af [diff] |
sandbox/linux: Allow fnctl on android for ashmem-memfd When ashmem is implemented by memfd on android, setting the r/w protection uses fcntl Bug: 1299437 Change-Id: I277b6aa495a9ec9ce6d1f370a982a45f57270198 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3475612 Reviewed-by: Egor Pasko <pasko@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Reviewed-by: Alex Ilin <alexilin@chromium.org> Commit-Queue: Alex Ilin <alexilin@chromium.org> Cr-Commit-Position: refs/heads/main@{#975773} NOKEYCHECK=True GitOrigin-RevId: 4ca2106bc0f70bedb95b229d116e86d6491846de
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.