Do IWYU for base/functional/callback.h in various files

Selectively add callback.h to some files that use it. In some cases,
replace incorrect callback_forward.h usage. This is split off from an
upcoming //mojo change that breaks the build for the files in this CL.

Change-Id: I7d0c8a2792b04ba443e58cb7045242f4dd69e50e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7230946
Owners-Override: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1555037}
NOKEYCHECK=True
GitOrigin-RevId: 2c055d73dc48ffdbad16e643a9d50a6e9d0afecd
2 files changed
tree: 14c3908f701d85fa13b7bd5a34c6f1105d592c94
  1. linux/
  2. mac/
  3. policy/
  4. win/
  5. BUILD.gn
  6. COMMON_METADATA
  7. constants.h
  8. DEPS
  9. DIR_METADATA
  10. features.cc
  11. features.gni
  12. features.h
  13. OWNERS
  14. README.md
  15. 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.