0
Files
src/sandbox
Mark Rowe 7b3962fe2e Remove logic related to macOS 10.14 from sandbox profiles
All supported macOS versions are newer than macOS 10.14 so there's no
need for this logic to be conditional.

Change-Id: I8b6410e8e38c490601e8d5912dc49f36d98e6849
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5459937
Commit-Queue: Mark Rowe <markrowe@chromium.org>
Auto-Submit: Mark Rowe <markrowe@chromium.org>
Reviewed-by: Elly FJ <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1289590}
2024-04-18 21:32:27 +00:00
..

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.