Fix presubmit warning in process_mitigations_unittest.cc

To wit:
  found MAYBE_ defined without corresponding test
    CheckWin10MsSignedWithIntercept_Success

Change-Id: Ic41f072edf28793f26371998b6a0b1ccb019ee05
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3387829
Commit-Queue: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Alex Gough <ajgo@chromium.org>
Cr-Commit-Position: refs/heads/main@{#959269}
NOKEYCHECK=True
GitOrigin-RevId: 70d58f2372e38213fea03e55a405aee2cd8211d4
1 file changed
tree: f89f10b0dde213db8d0d453689f859531b2cb959
  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.