| commit | 9aa5a80028c737fc1631e9f73f2987d57be140fb | [log] [tgz] |
|---|---|---|
| author | Will Harris <wfh@chromium.org> | Sat Oct 30 00:17:45 2021 |
| committer | Copybara-Service <copybara-worker@google.com> | Sat Oct 30 00:33:36 2021 |
| tree | e6e04f2850847335df1c725ac86f28206166a8eb | |
| parent | 2c1b85d01a7ab7827ec3a3a80d9156f6f7fb6170 [diff] |
Create a unique App Container id for each App Container test. If multiple tests that use App Container were running concurrently there was potential for one test to manipulate another test's profile. This CL changes the App Container id to be based on the test name rather than just the program name. BUG=1264188 Change-Id: I0fd188426407dcddee5273678ac3304453d8cdee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3253948 Reviewed-by: Alex Gough <ajgo@chromium.org> Commit-Queue: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/main@{#936620} NOKEYCHECK=True GitOrigin-RevId: 1e4afbcb3e5afc2efc62f8bf107514165884fdbe
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.