b31357b16f
"alarm and "mremap" syscalls are allow-listed for ScreenAI service, as needed by libchromescreenai.so 127.0 (updated in crrev.com/c/6014185). Bug: 378472917,378928754 Change-Id: Id440c841d2d4bbe314a679c3520bd3e41153d6ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6011106 Reviewed-by: Matthew Denton <mpdenton@chromium.org> Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Cr-Commit-Position: refs/heads/main@{#1382588}
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.