commit | 2e720250672f6aa157d1b622c16f7ae2ac76c35d | [log] [tgz] |
---|---|---|
author | Yuwei Huang <yuweih@chromium.org> | Thu May 19 22:12:42 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 19 22:12:42 2022 |
tree | b59a251baef2d6ceaa3d9a68ff4bf0a00f346ca0 | |
parent | 182cdb2a4f6c917fd6d64670bb5b55add0e41726 [diff] |
[remoting][win][webauthn] Fix extension wakeup The webauthn extension wakeup mechanism doesn't work on Windows. It turns out the problem is that RemoteWebAuthnExtensionNotifier::NotifyStateChange() is invoked from the network process, which does not have access to the LocalAppData directory, so the write to the extension wakeup file will fail. This CL fixes this problem by having the network process make an IPC to the high-privilege desktop process, which writes the wakeup file on the desktop process. (cherry picked from commit 2ad53d9a92fad04b294850bec3623fbea79e7e3c) Bug: 1325523 Change-Id: I5ddc5beee14c038fd0713a3806578769ae588c20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3650999 Commit-Queue: Yuwei Huang <yuweih@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Reviewed-by: Joe Downing <joedow@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1004927} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3655244 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Yuwei Huang <yuweih@chromium.org> Commit-Queue: Ken Buchanan <kenrb@chromium.org> Cr-Commit-Position: refs/branch-heads/5060@{#125} Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}
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.