7dc7007060
1.Replace unique_ptr<string> with optional<string> to reduce memory allocations. 2.Use const string& instead of const char*, introduce LIFETIME_BOUND to clarify the lifetime, and mark the method with const, mutable, etc. to ensure the security of the sandbox code. Bug: None Change-Id: I1cd4f548e5ea6600a8c84c54860a7347bd7b7f35 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6342732 Commit-Queue: Ho Cheung <hocheung@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Reviewed-by: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/main@{#1431908}
Sandbox Library
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.