sandbox: allow PR_GET_TAGGED_ADDR_CTRL

prctl(PR_GET_TAGGED_ADDR_CTRL, ...) lets Chromium set and get the
current memory tagging mode via the partition allocator.

Also gates PR_PAC_RESET_KEYS to AArch64.

Bug: 1137393, 1445768
Change-Id: I4412a7f8bf483de778b21aa71a24c33474fed519
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4526176
Reviewed-by: Matthew Denton <mpdenton@chromium.org>
Commit-Queue: Matthew Denton <mpdenton@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1145071}
NOKEYCHECK=True
GitOrigin-RevId: 2845592fa1005c6ca70dc8507e37f8fc7c99b9f1
1 file changed
tree: d4cd756e6cc336c4c0cc47b255276c19c6138e8f
  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.