[fuchsia] Obtain VMEX capability via VmexResource

Migrate all Chromium binaries from using ambient VMEX to obtaining the
ability to create executable pages via the VmexResource service.

Bug: 1290907
Change-Id: I0cb76df5d5524e56b03e1a82d7fb778c8bae797f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3825933
Auto-Submit: Wez <wez@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Reviewed-by: David Dorwin <ddorwin@chromium.org>
Quick-Run: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1145291}
GitOrigin-RevId: dc2cf3d56be7fa98a0d292f3331fa59ffa1383eb
1 file changed
tree: 26cea3c91d4f2c87ae2a734b01c54055069b61f8
  1. linux/
  2. mac/
  3. policy/
  4. win/
  5. BUILD.gn
  7. constants.h
  8. DEPS
  10. features.cc
  11. features.gni
  12. features.h
  13. OWNERS
  14. README.md
  15. sandbox_export.h

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.