Reland: [Windows] Remove old sandbox Sid class.

This CL removes the old sandbox Sid class and moves all users to the
new class in base. This reland fixes the sandbox_poc to use the new
Sid class which was missing in the original CL.

Bug: 1266853
Change-Id: Ic5c9f92d53f94ffe4d5b43bc2ba923fced73c7e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3277532
Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: James Forshaw <forshaw@chromium.org>
Cr-Commit-Position: refs/heads/main@{#941477}
NOKEYCHECK=True
GitOrigin-RevId: 460112401fbfd7e55bc9a29982a6104a1cf3c944
32 files changed
tree: 15531ca6200342031ce24ec5731bc2bbde29a727
  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.