Hi all,
I was wondering whether anyone uses KeePassXC with the Firefox browser add-on on Zorin OS. I can’t get the browser add-on to recognize the app. I spent a better part of yesterday trying to figure out a solution but just can’t seem to get it to work. Any help?
probably because keepass is installed via flatpak (default way of installing things, also they’re sandboxed)
The issue is not KeePassXC flatpak, but both Firefox and KeepassXC flatpak.
I use KeepassXC flatpak and native Firefox and works flawlessly.
In my opinion, the web browser is the single most important application that should be sandboxed on a system. We use them to access nearly everything on the Internet, including resources that are routinely laden with obfuscated JavaScript.
Every attempt should be made to separate the browser from the host system, and circumventing that safeguard in order to facilitate direct access to your password database is risky at best.
Edit: I don’t mean to suggest that I have the perfect solution either, but I keep everything sandboxed and just opt for KeePassXC’s native global hotkey for auto-filling credentials.
I never tested, but I think you can do either way: Firefox native and KeePassXC flatpak; or Firefox flatpak and KeePassXC native
What cannot happen is both flatpak, cause they won’t work together…
Well, if you test the other way around, tell us, cause I can only tell with KeePassXC flatpak and Firefox native
Ended up trying that, but it didn’t work. “Key exchange unsuccessful”, it said. Ended up installing both FF and KPXC over apt and it’s working like a charm.
I DID IT!!! I DID IT!!! I INSTALLED FIREFOX FROM SOURCE (TAR.BZ2) AND RUN KPXC FROM THE APPIMAGE!!! LET’S GOOO!
Have you activated the browser integration in KeepassXC ?
I’m using Librewolf (a Firefox fork) and have the same issue.
Just check Firefox messaging folder exists in your home
ls -l ~/.mozilla/native-messaging-hosts
In my case, I needed to create a symlink to make it work with my browser
ln -s ~/.mozilla/native-messaging-hosts ~/.librewolf/native-messaging-hosts
Maybe you could apply a similar workaround. Hope this helps