-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KeePassXC Flatpak Integration Does Not Function #381
Comments
This is an issue with the flatpak browser. See: keepassxreboot/keepassxc#2656 |
I have been having this issue for quite some time now. i have run both keepassxc and brave with debug output and i see a Lack of Direct References to KeePassXC's Unix Domain Socket: There is no explicit reference to the KeePassXC's Unix Domain socket (e.g., /run/user/1000/app/org.keepassxc.KeePassXC/org.keepassxc.KeePassXC.BrowserServer). This could be important because Brave needs access to this socket for the KeePassXC extension to work properly. adding using:
also i have seen references to a proxy daemon of sorts that is expected by keepassxc, but i cant find that on my system either. hope we can think through this and find a solution! puc |
@puccaso, This is incorrect for Also in this file you should specify the path to the This is what I got in the end: $ flatpak override --user com.brave.Browser --filesystem=xdg-run/app/org.keepassxc.KeePassXC
$ cat > ~/.var/app/com.brave.Browser/config/BraveSoftware/Brave-Browser/NativeMessagingHosts/org.keepassxc.keepassxc_browser.json <<EOF
{
"allowed_origins": [
"chrome-extension://pdffhmdngciaglkoonimfcmckehcpafo/",
"chrome-extension://oboonakemofpalcgghocfoadofidjkkk/"
],
"description": "KeePassXC integration with native messaging support",
"name": "org.keepassxc.keepassxc_browser",
"path": "/var/config/BraveSoftware/Brave-Browser/NativeMessagingHosts/keepassxc-proxy",
"type": "stdio"
}
EOF
$ git clone https://github.com/varjolintu/keepassxc-proxy-rust.git
$ cd keepassxc-proxy-rust
$ RUSTFLAGS="$RUSTFLAGS -C target-feature=+crt-static" cargo build --release
$ cp target/release/keepassxc-proxy ~/.var/app/com.brave.Browser/config/BraveSoftware/Brave-Browser/NativeMessagingHosts Good luck |
Hello,
I'm experiencing an issue where Flatpak KeepassXC and Flatpak Brave browser will not communicate with each other as expected. I've tried many solutions in other github issues and forum posts, and none work.
Shouldn't the default permissions of both the Brave flatpak and KeePassXC flatpak be altered so that they work together out of the box?
Also, what can I do as a temporary solution?
The text was updated successfully, but these errors were encountered: