| commit | 3e7369b9c68a63fce4c248a660991d80c85302e3 | [log] [tgz] |
|---|---|---|
| author | Emily Andrews <emiled@microsoft.com> | Tue Jan 11 20:36:32 2022 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 11 20:55:00 2022 |
| tree | f8cbf2a34e1a9f9e195636df0f1a2ecf1fc1e612 | |
| parent | e4cac7d531b1986ca0ff6ff763890c051e999ffd [diff] |
Win: Move parts of the AppContainerBase up into the AppContainer Interface definition This will hopefully prevent some PGO SBOX_ERROR_CANNOT_WRITE_VARIABLE_VALUE crashes we've been seeing in the wild and create better code cleanliness. Bug: 1177001 Change-Id: I71259a2579742a3b783262ab16c1980011827cb7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3378485 Reviewed-by: James Forshaw <forshaw@chromium.org> Reviewed-by: Alex Gough <ajgo@chromium.org> Commit-Queue: Emily Andrews <emiled@microsoft.com> Cr-Commit-Position: refs/heads/main@{#957697} NOKEYCHECK=True GitOrigin-RevId: b5562e7049b33e5e169908124d52ce75737059b9
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.