| commit | c75ffb288f417b341761f586217cff935d727e18 | [log] [tgz] |
|---|---|---|
| author | Matthew Denton <mpdenton@chromium.org> | Thu Jul 22 15:37:08 2021 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jul 22 15:49:38 2021 |
| tree | 079fac0e4869661406ab72d7914e08b9aaf97200 | |
| parent | dbf98d3772f625af95e6bfb020d5e9ef9800ef54 [diff] |
Syscall wrappers: Linux sandbox: Fix SyscallWrappers.Stat test stat() syscall can return EOVERFLOW on 32-bit so SyscallWrappers.Stat can't just test for EFAULT. Bug: 1231701, 1232001 Change-Id: I935a648ea60bec8aadbfe54e9ffd7c15fb9b7c08 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3044253 Reviewed-by: Alex Ilin <alexilin@chromium.org> Commit-Queue: Matthew Denton <mpdenton@chromium.org> Cr-Commit-Position: refs/heads/master@{#904338} NOKEYCHECK=True GitOrigin-RevId: addd83ba2d12080ec4597578b903a10c2c968a69
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.