Rename "base/macros.h" => "base/ignore_result.h"

This file only contains ignore_result() and is no longer a collection of
macros.

This change fixes a couple of missing IWYU removals as well.

Bug: 1010217
No-Try: true
Change-Id: Iaad1aaa48343e86b0429898bd55e4f0c56222852
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3279210
Commit-Queue: Peter Boström <pbos@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Owners-Override: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#941411}
NOKEYCHECK=True
GitOrigin-RevId: 2e6be1400ab678f21d871d0d3a1199912967324f
6 files changed
tree: 4d50665d38ebc1b8cf69666eaa1be258f7f5bb3b
  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.