4ab0f932f4
Repeatedly use grep to find all the files in various dirs that includes base/stl_util.h but do not use any functions provided by base/stl_util.h and base/cxx*_backports.h, and then remove the base/stl_util.h include from them. Files that include base/stl_util.h, but actually needs base/cxx*_backports.h, will be dealt with separately. Bug: 1194078 Change-Id: I50796fb91c03eed1b63ce901005818ba2ec3d94c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2909802 Commit-Queue: Nico Weber <thakis@chromium.org> Auto-Submit: Lei Zhang <thestig@chromium.org> Reviewed-by: Nico Weber <thakis@chromium.org> Owners-Override: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#885634}
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.