0
Files
src/sandbox
Thiabaud Engelbrecht 90d66f8045 [self_freeze] Add function to allow compacting our own memory
We use MADV_PAGEOUT in order to swap out non-shared, non-file-backed pages that we don't need. This will be used when we go to background but are not frozen/compacted by App Freezer. This function is currently not called anywhere, so this CL should not change any behavior.

Bug: 344547190
Change-Id: Ie2bd754ba06b5cae6769221396471eb74d495522
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5887346
Reviewed-by: Matthew Denton <mpdenton@chromium.org>
Reviewed-by: Benoit Lize <lizeb@chromium.org>
Reviewed-by: Brian Geffon <bgeffon@chromium.org>
Commit-Queue: Thiabaud Engelbrecht <thiabaud@google.com>
Cr-Commit-Position: refs/heads/main@{#1372231}
2024-10-22 19:05:37 +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.