Refactor building of startup information.

Adds a wrapper to contain building proc_thread_attribute_* and to
provide storage for pointed-at items for call to
CreateProcessAsUserW().

This does not change functionality, but moves code from target_services
into a helper.

Bug: 1050359
Change-Id: I3d25e028638b2ea6f2917de1154be7a99fdf5971
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2330736
Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Alex Gough <ajgo@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#794618}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: e2c08269fa3987040a77629e1461c4ec2c3ed623
6 files changed
tree: dc3f4b32195b3317b451b6e8edb03b29b78df1d0
  1. linux/
  2. mac/
  3. policy/
  4. win/
  5. BUILD.gn
  6. constants.h
  7. DEPS
  8. features.gni
  9. ipc.dict
  10. OWNERS
  11. README.md
  12. 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.