Prevent sandbox::TestRunner from reusing Policy

In Chrome we only use each Policy for a single process, while
in tests we often apply the same policy to multiple processes.

The critical part of this change is the CHECK in controller.cc,
everything else is introducing fresh |TestRunner|s for each call
to RunTest(). Where the runner setup was simple we introduce
multiple TestRunner within each TEST() function. Where the setup
is more complex we provide a helper returning a
std::unique_ptr<TestRunner>() and call it multiple times to reset
the runner.

Bug: 1270309,1291884
Change-Id: I353051c59e0fb43187961f435530795abd81fc08
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3426302
Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Alex Gough <ajgo@chromium.org>
Cr-Commit-Position: refs/heads/main@{#967561}
NOKEYCHECK=True
GitOrigin-RevId: 137d2680a17eb69b63130b0015407ae105cb3cf2
12 files changed
tree: f7fc0437750c8a146e7570ffd686559b4cb60d3f
  1. linux/
  2. mac/
  3. policy/
  4. win/
  5. BUILD.gn
  6. COMMON_METADATA
  7. constants.h
  8. DEPS
  9. DIR_METADATA
  10. features.gni
  11. ipc.dict
  12. OWNERS
  13. README.md
  14. sandbox_export.h
README.md

Sandbox Library

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.