commit | 7f725ac9731b9b289fade68835b929a8faf68693 | [log] [tgz] |
---|---|---|
author | Maksim Sisov <msisov@igalia.com> | Wed Nov 03 13:23:13 2021 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Nov 03 13:35:43 2021 |
tree | 8bb6c401f1255bbb699fee01ba16c84af2fdc714 | |
parent | 30ef2b4599d0b5eb2fed4eed04671eb7c49232ce [diff] |
ozone: //sandbox: clean up from USE_X11 This is another CL that removes USE_X11 define and gn arg usage from //sandbox. Bug: 1096425 Change-Id: I1abd789a707c8ae65c4afd6591c0531b852c8383 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3257554 Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Maksim Sisov <msisov@igalia.com> Cr-Commit-Position: refs/heads/main@{#937847} NOKEYCHECK=True GitOrigin-RevId: 8d9e28e87b31666ee06a53ab2eb55bc4a5348bcb
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.