f68d83037d
The new Ubuntu picked up a newer glibc, which included this change: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=efc6b2dbc47231dee7a7ac39beec808deb4e4d1f Now the pipe() function is implemented in terms of the pipe2 syscall, so we need to allow it on all architectures, not just aarch64. Bug: 40248746 Change-Id: I01e6ca1e6e48b71d818e994ad192e55f6d4484df Fixed: 40273116 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5856940 Commit-Queue: Nico Weber <thakis@chromium.org> Auto-Submit: David Benjamin <davidben@chromium.org> Reviewed-by: Nico Weber <thakis@chromium.org> Reviewed-by: Matthew Denton <mpdenton@chromium.org> Cr-Commit-Position: refs/heads/main@{#1354745}
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.