| commit | 62184c7452a892af563152411e68adc741bde908 | [log] [tgz] |
|---|---|---|
| author | Will Harris <wfh@chromium.org> | Thu May 18 17:20:12 2023 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu May 18 17:39:11 2023 |
| tree | 3ed33385fa6ba33bfbd635b7b1730b61afe41266 | |
| parent | bd1787925e5de40b143e9300e500eabf595df233 [diff] |
Remove renderer environment filtering feature and enable by default. Also, add some tests, as these were missing from the previous CL. BUG=1316641,1403087 Change-Id: Iab5803962504bcd53b6474c1730258f60eb4068b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4545784 Reviewed-by: Alex Gough <ajgo@chromium.org> Commit-Queue: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/main@{#1146014} NOKEYCHECK=True GitOrigin-RevId: 0cddbcd5426a327e872d8d77c632ec29a3f28e54
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.