| commit | cfac2fd3bcad20801246e96d7ab5327df5f71ab0 | [log] [tgz] |
|---|---|---|
| author | Emily Andrews <emiled@microsoft.com> | Wed Nov 10 20:36:36 2021 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Nov 10 20:50:59 2021 |
| tree | e515e3f0ed3bdda8cfd61146764245859090b492 | |
| parent | 30cefb0799c011684ca425612c1f574fe489ce7c [diff] |
Add Render Process Sandbox Policy feature tests This is primarily a Windows change, but some refactoring was necessary in order to make RendererSandboxedProcessLauncherDelegate usable in test code and this class exists on multiple flavors. Bug: 1266582 Change-Id: Id9aefb3e3eed2e3e375c8f14e0e90127cb86fc3e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3260947 Reviewed-by: Will Harris <wfh@chromium.org> Reviewed-by: Jonathan Ross <jonross@chromium.org> Commit-Queue: Emily Andrews <emiled@microsoft.com> Cr-Commit-Position: refs/heads/main@{#940462} NOKEYCHECK=True GitOrigin-RevId: cbbfffe534a0017c63f27229096289cb220937c6
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.