| commit | 31a4e9056d8896a2da55995f45a05445c31e6d08 | [log] [tgz] |
|---|---|---|
| author | Clemens Backes <clemensb@chromium.org> | Thu Jul 15 08:09:19 2021 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jul 15 08:23:49 2021 |
| tree | d88e95ff3c670906378be63e8d3358f65ec5cee3 | |
| parent | 10c64d79352ee96466bf55262a0992072bd67a8d [diff] |
[sandbox] Restrict pkey_alloc flags The "flags" argument to pkey_alloc must currently always be zero. Enforce this via the sandbox to pretect against future extensions. R=rsesek@chromium.org Bug: chromium:1229359 Change-Id: I9922701728facbe5a44466bb6fc8534ec797be27 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3028921 Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#901869} NOKEYCHECK=True GitOrigin-RevId: 59d1fff9ed5d72b4ecf4d48f7e0710c6e5c19bfc
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.