If I have firefox open and run ps aux | grep -i keepassxc-proxy I can see the binary running, however it does not happen when only Brave is running. So I believe the problem is that keepassxc-proxy is not launched by Brave? KeePass HTTP support for use with Chrome and Firefox extensions. Mac users may notice similarities between KeePassXC and KeePassX, a Mac-only client based on KeePass. Net Framework, so that is resolved as well. And also have the socket file /run/user/1001/app// KeePassXC does not rely on the Microsoft. The file /run/user/1001/ is a symbolic link to itself, what is correct. The Unix Domain socket path check also seems correct.I believe because the command pgrep brave returns multiple PIDs (while firefox only returns one PID) Sudo strace -f -p $(pgrep brave) 2>&1 | grep keepass When I try monitoring the process with Brave The keepassxc-proxy binary is not running, and I can not run it manually."description": "KeePassXC integration with native messaging support", "chrome-extension://oboonakemofpalcgghocfoadofidjkkk/" "chrome-extension://pdffhmdngciaglkoonimfcmckehcpafo/", ~/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts/_browser.json The path for the native message script for Brave browser is not indicated. I followed these guidelines to track the problem. It should ask for a new association key when pressing connect and connect to the database KeepassXC-Browser should connect to KeepassXC Database. KeepassXC-Browser can not connect to the KeepassXC Database.Open the KeepasXC aplication and database (all well configured, and Browser Integration with Brave activated).The problem does not happen when Brave stable release (v1.45.131 ) is used. That’s it, now you would be able to autofill passwords from KeePass in Microsoft Edge browser in Linux.KeepassXC-Browser does not connect to KeepassXC when Brave Beta is used. If all goes well, you would be able to see a screen similar to the one shown below. In the above path, replace “ ar” with your user id and “ microsoft-edge-dev” with “ microsoft-edge-beta“, if you are using the beta version of the browser.Īs a next step, click the plugin icon in the browser and create a connection between the browser and KeePassXC application. In my machine ( Kubuntu), the path is “ /home/ar/.config/microsoft-edge-dev/NativeMessagingHosts/“. Select “Chromium” as browser type in the Config Location, provide the config path for Edge.Navigate to the “Advanced” tab of “Browser Integration” and select “Use a custom browser configuration location:”.Select the “Browser Integration” side menu and ensure that “Chromium” is selected in the “General” tab.Open the KeePassXC application and navigate to the settings page.If you haven’t downloaded the plugin yet, you can download it from the Edge Add-Ons site Configuration Steps
0 kommentar(er)
