Later on in the logs I see the following which look like errors relating to the above command. I see some registry queries for NativeMessagingHosts, chrome reading the _browser_brave.json file and the keepassxc-proxy getting created(?)/read.Īdditionally I see there's a command line executed by I assume some method similar to Start > Run (windows enviroments are not my forte) C:\Windows\system32\cmd.exe /d /c "C:\Program Files\KeePassXC\keepassxc-proxy.exe" chrome-extension://oboonakemofpalcgghocfoadofidjkkk/ -parent-window=0 \\.\pipe\.94d8e70637609cd3 I've isolated a chunk of Process Monitor logs filtered around just the Chrome process while I opened and the browser extension and clicked Reload. The troubleshooting guide does not have instructions for how to "Find the native messaging configuration path with strace" in Windows. However, since I have this working on Firefox now, I assume this isn't the problem? Checking the AppData/Local/KeePassXC json files There are no steps on how to verify this in the troubleshooting guide for Windows. □ Check if keepassxc-proxy is launched and running. Uninstalling and Reinstalling KeePassXC and trying Firefox again, and it now appears to be working but still failing in Chrome. Running the MSI installer and selecting Repair did populate it with the above.įirefox registry entry: HKEY_CURRENT_USER\\Software\\Mozilla\\NativeMessagingHosts\\ Name: (Default), Type: REG_SZ Data: C:/Users/glowbox-user/AppData/Local/KeePassXC/_browser_tor-browser.json Note When first inspected, this registry's data value was blank. I have purged the Connected Databases list from the extension in Chrome.Ĭhrome registry entry: HKEY_CURRENT_USER\\Software\\Google\\Chrome\\NativeMessagingHosts\\ Name: (Default), Type: Reg_SZ, Data: C:/Users/glowbox-user/AppData/Local/KeePassXC/_browser_brave.json
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |