| commit | 5ed366d12b578f64863cf9549802405674de6b3e | [log] [tgz] |
|---|---|---|
| author | Alex Gough <ajgo@chromium.org> | Tue Aug 10 22:29:28 2021 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Aug 10 22:42:50 2021 |
| tree | e3b70311bad22c4f13e839781f2a31c1240a2d37 | |
| parent | a1518eea599608369b3b0cc56a54b854534ab79a [diff] |
Specify ChromeOS service sandboxes in mojom This moves to using the ServiceSandbox mojom attribute to select the sandbox, and removes reference from service_sandbox_type.h which can now be deleted. The following services now have their sandbox defined in their mojom file:- ImeService, TtsService, RecordingService, AssistantAudioDecoderFactory, LibassistantService No functional changes, see linked bug for details. Bug: 1210301 Change-Id: I1791d1c6b66f7ad2e5bb7827c6c21e54ef25b19c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3073582 Reviewed-by: Leo Zhang <googleo@chromium.org> Reviewed-by: Chris Palmer <palmer@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> Reviewed-by: David Tseng <dtseng@chromium.org> Commit-Queue: Alex Gough <ajgo@chromium.org> Cr-Commit-Position: refs/heads/master@{#910509} NOKEYCHECK=True GitOrigin-RevId: f31f09842f1f3dd680227cc10fcdf9ed598eabb1
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.