66fac67edf
4GB is not enough, since the normal GPU limit wasn't used for the new sandbox type. Bug: b/311447339 Change-Id: I2bc11891b6f542747c8242efe30b2b4bce50c5a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5039228 Reviewed-by: James Forshaw <forshaw@chromium.org> Auto-Submit: John Abd-El-Malek <jam@chromium.org> Commit-Queue: James Forshaw <forshaw@chromium.org> Cr-Commit-Position: refs/heads/main@{#1225976}
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.