| commit | dc0f5063db7e2c2a51c3af9437fcbd6f21de7cb7 | [log] [tgz] |
|---|---|---|
| author | Tomasz Tylenda <ttylenda@chromium.org> | Tue Nov 02 12:30:23 2021 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Nov 02 12:41:13 2021 |
| tree | c2e6d35b689cd5f3dbb318d7e3a3dfd4882a2a65 | |
| parent | 7c632e9e73b31fe82df998aaac546762d90d2c83 [diff] |
Revert "Remove DISALLOW_IMPLICIT_CONSTRUCTORS()" This reverts commit 5625bdd79190d1633f4817d25cae6b68727c89cd. Reason for revert: breaks compile on https://ci.chromium.org/p/chrome/builders/ci/chromeos-eve-chrome and https://ci.chromium.org/p/chrome/builders/ci/chromeos-kevin-chrome Original change's description: > Remove DISALLOW_IMPLICIT_CONSTRUCTORS() > > This removes the macro definition and presubmit checks and all existing > instances are inlined. > > IWYU is left as a separate step until all DISALLOW_* macros are removed. > > Bug: 1010217 > Change-Id: Ibc4d90d6a1f244a01e65cd3c5a9c50e5419ea5a1 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3257088 > Reviewed-by: Lei Zhang <thestig@chromium.org> > Owners-Override: Lei Zhang <thestig@chromium.org> > Commit-Queue: Peter Boström <pbos@chromium.org> > Cr-Commit-Position: refs/heads/main@{#937250} Bug: 1010217 Change-Id: I6341be7521fde453b671d6b339eef796a49847ac No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3256685 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: Henrik Boström <hbos@chromium.org> Owners-Override: Henrik Boström <hbos@google.com> Commit-Queue: Tomasz Tylenda <ttylenda@chromium.org> Cr-Commit-Position: refs/heads/main@{#937292} NOKEYCHECK=True GitOrigin-RevId: 15aa98232cf7d22d10990b9ab532a3b8c61db7ee
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.