| commit | 2aea2e93f485d515e7ac880d1d4a5e0168a25539 | [log] [tgz] |
|---|---|---|
| author | Stephan Hartmann <stha09@googlemail.com> | Mon Feb 07 20:09:57 2022 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Feb 07 20:23:34 2022 |
| tree | ca026a6b0a26be48260589540750d64f79c930ca | |
| parent | 0c14b084cc94801c8620865d3c509996f6d17c5b [diff] |
sandbox: build if glibc 2.34+ dynamic stack size is enabled Compilation of sandbox fails when using dynamic stack size in glibc 2.34 or newer. This is because the value is not a literal anymore but obtained through sysconf. To avoid this, use memset to put zeros in the buffer. Change-Id: Ia479e0f799b77a10a00197aaaa0500e62546f458 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3436947 Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org> Commit-Queue: José Dapena Paz <jdapena@igalia.com> Cr-Commit-Position: refs/heads/main@{#967943} NOKEYCHECK=True GitOrigin-RevId: 28ac6a15411d01301e171b8a8b0019abd57589b9
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.