commit | 8371cb55a23e1905c631aeed65818d71dee37696 | [log] [tgz] |
---|---|---|
author | Emily Andrews <emiled@microsoft.com> | Mon Jan 24 18:27:26 2022 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Jan 24 18:44:34 2022 |
tree | 6d6f6bd5f323f3319b35bd905aa2da96d5537d83 | |
parent | 9cf541baea7e4df37d502dd51fb12246c43b36a4 [diff] |
Win: Create a pit of success for SandboxPolicyFeatureTests This change moves some checks into base Validate* methods. Also adds more virtual functions for Expected behaviors. Bug: 1286104 Change-Id: I7fc01d5d77a1da8e30c22a9dfb9e763caa7f265e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3379646 Reviewed-by: Alex Gough <ajgo@chromium.org> Reviewed-by: Bo Liu <boliu@chromium.org> Commit-Queue: Emily Andrews <emiled@microsoft.com> Cr-Commit-Position: refs/heads/main@{#962578} NOKEYCHECK=True GitOrigin-RevId: 515ee894cc1aa1e8b88e93b8c279121ffc3ce01d
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.