
This reverts commit302442a4b4
. Reason for revert: Fixing typo Original change's description: > Revert "WebUI Mojo Bindings: Remove use_typescript_sources" > > This reverts commit2599dd89d8
. > > Reason for revert: breaks compile for chromeos dbg > https://ci.chromium.org/ui/p/chromium/builders/try/linux-chromeos-compile-dbg/1632716 > > FileNotFoundError: [Errno 2] No such file or directory: 'gen/mojom-webui/chrome/test/data/webui/chromeos/web_ui_test.mojom-webui.js' > > Original change's description: > > WebUI Mojo Bindings: Remove use_typescript_sources > > > > The use_typescript_sources parameter was confusing to reviewers (not > > clear what "sources" it refers to, or that it is WebUI-specific), and > > is now default true/on which is the reverse of convention and confuses > > developers about when the parameter needs to be specified. > > > > Renaming it to generate_webui_js_bindings, changing to default "off", > > and limiting the parameter to ChromeOS Ash since WebUI bindings always > > use TypeScript on other platforms. > > > > In this CL removing use_typescript_sources and updating a few > > remaining users. > > > > Bug: 1002798 > > Change-Id: Ic6ee29be22b65bb2d4b1f5fda013766b3c06bd5e > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5115946 > > Reviewed-by: Reilly Grant <reillyg@chromium.org> > > Reviewed-by: Robert Sesek <rsesek@chromium.org> > > Commit-Queue: Rebekah Potter <rbpotter@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#1237670} > > Bug: 1002798 > Change-Id: I84c93e8c09ac384f18440e3eb791cf8b5b5d4b22 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5124793 > Auto-Submit: Joel Hockey <joelhockey@chromium.org> > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Commit-Queue: Shibalik Mohapatra <shibalik@chromium.org> > Owners-Override: Shibalik Mohapatra <shibalik@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1237850} Bug: 1002798 Change-Id: I7b89113e48969343f7683636b63525ba8ea2006b No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5125264 Reviewed-by: Alex Gough <ajgo@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/main@{#1238216}
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.