KeepassXC-Browser does not connect to KeepassXC in Brave Beta

Feedback Beta Builds
1

Description of the issue:

KeepassXC-Browser does not connect to KeepassXC when Brave Beta is used. The problem does not happen when Brave stable release (v1.45.131 ) is used.

How can this issue be reproduced?

  1. Open the KeepasXC aplication and database (all well configured, and Browser Integration with Brave activated)
  2. Install the KeepassXC-Browser add-on
  3. KeepassXC-Browser can not connect to the KeepassXC Database

Expected result:

KeepassXC-Browser should connect to KeepassXC Database. It should ask for a new association key when pressing connect and connect to the database

Brave Version( check About Brave):

version 1.46.110 Chromium:107.0.5304.1100 (Official Build) beta (64-bit)

Additional Information:

I followed these guidelines to track the problem. My findings are the following

  1. The path for the native message script for Brave browser is not indicated. I found it here:
    ~/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts/org.keepassxc.keepassxc_browser.json

  2. The content of the file seems correct:

{
    "allowed_origins": [
        "chrome-extension://pdffhmdngciaglkoonimfcmckehcpafo/",
        "chrome-extension://oboonakemofpalcgghocfoadofidjkkk/"
    ],
    "description": "KeePassXC integration with native messaging support",
    "name": "org.keepassxc.keepassxc_browser",
    "path": "/home/david/software/keepassXC/KeePassXC-2.7.4-x86_64.AppImage",
    "type": "stdio"
}
  1. The keepassxc-proxy binary is not running, and I can not run it manually. When I try monitoring the process with Brave

sudo strace -f -p $(pgrep brave) 2>&1 | grep keepass

it does not work. I believe because the command pgrep brave returns multiple PIDs (while firefox only returns one PID)

  1. The Unix Domain socket path check also seems correct.
    The file /run/user/1001/org.keepassxc.KeePassXC.BrowserServer is a symbolic link to itself, what is correct. And also have the socket file /run/user/1001/app/org.keepassxc.KeePassXC/org.keepassxc.KeePassXC.BrowserServer

So I believe the problem is that keepassxc-proxy is not launched by Brave?

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.

Some extra details:

KeePassXC - Version 2.7.4
Revision: 63b2394
Distribution: AppImage

Qt 5.15.2
Debugging mode is disabled.

Operating system: Ubuntu 20.04.5 LTS
CPU architecture: x86_64
Kernel: linux 5.14.0-1054-oem

Enabled extensions:

  • Auto-Type
  • Browser Integration
  • SSH Agent
  • KeeShare
  • YubiKey
  • Secret Service Integration

Cryptographic libraries:

  • Botan 2.19.1

KeePassXC-Browser - 1.8.3.1
Operating system: Linux x86_64
Browser: Chrome/Chromium 107.0.0.0

3 Likes
2

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.