[Windows] Remove CreateProcess hooks for SUBSYS_PROCESS.

This CL removes the CreateProcess hooks for the SUBSYS_PROCESS sandbox
policy. It leaves in the other necessary hooks so doesn't remove the
entire subsystem.

Bug: 1058631
Change-Id: Ib37e54a5e1d65c038c429556c3d250cd49da0c14
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3293426
Reviewed-by: Alex Gough <ajgo@chromium.org>
Commit-Queue: James Forshaw <forshaw@chromium.org>
Cr-Commit-Position: refs/heads/main@{#944191}
NOKEYCHECK=True
GitOrigin-RevId: dc67fb39a46834d27e65f5a528d456c9c2f7ad33
15 files changed
tree: e5e99e4479269e1da2a0c59bed81f31d19768a8c
  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.