commit | 0375dd337317f632d5694208a314032dac0cf2ed | [log] [tgz] |
---|---|---|
author | Wez <wez@chromium.org> | Mon Jan 10 22:39:25 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 10 22:39:25 2022 |
tree | 6de8039878c9776435c65d96968edfe95a62e121 | |
parent | d5196f6ec623d78cf564c1eba0e7499b94a4215f [diff] |
[fuchsia] Populate web_instance sandbox with only required services. This is a reland of https://chromium-review.googlesource.com/c/chromium/src/+/3353490 with validation of the NETWORK flag being provided when remote-debugging is enabled removed, to allow that enforcement to be landed separately. Callers provide services to WebInstanceHost for each web_instance.cmx that they want to launch. Internally the WebInstanceHost must explicitly allow-list the services that the component may actually use. Previously all services that the web_instance.cmx could possibly require would be allow-listed. WebInstanceHost now allow-lists only those services required by the features enabled in the CreateContextParams, to further guard callers against exploits. Enforcement of the NETWORK feature-flag is deferred to a follow-up CL, pending audit of all existing ContextProvider callers. The missing flag is nonetheless added for various test suites, in advance of it actually being enforced. This affects both tests that make network requests, and those that implicitly require networking, such as DevTools tests. Bug: 1071067, 1020273, 1209031, 1285964 Cq-Include-Trybots: luci.chrome.try:fuchsia-fyi-astro Change-Id: I954291da0b60fddc701e22a5b68788b4ea15eaf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3379005 Commit-Queue: Wez <wez@chromium.org> Commit-Queue: Robert Sesek <rsesek@chromium.org> Auto-Submit: Wez <wez@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/main@{#957283}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.