I’m slowly piece mealing my way to Waterfox this weekend. One issue I’ve had is getting KeepassXC working.

I suspect this is more of a flatpak thing than a Waterfox thing. I’m not familiar with flatpak enough to know where I need to go to get it to work. If you have suggestions, let me know.

Right now I’m copying and pasting.

  • @crunchymunchytoast
    4•2 days ago

    I use librewolf from the aur so I’m not sure if this would apply (or if you’ve already tried it), but try moving the “native-messaging-hosts” directory from the “.mozilla” directory to your waterfox directory in your home and then symlinking the waterfox directory to “.mozilla”

    KeepassXC technically only has support for Firefox (and other mainstream browsers) so it always puts the required files for the integration into that “.mozilla” directory.

    Speaking purely on speculation, waterfox in a flatpak should already have read/write access to whatever folder in your home it uses for user data so I’m assuming that the difference in where keepass puts the “native-messaging-hosts” is what’s causing your issue.

    If that’s not it though, you could likely use bubblejail to tweak the permissions of the waterfox container to grant it access to those folders. Or double check that browser integration is enabled in keepass.

    • @[email protected]OPEnglish
      1•2 days ago

      I would have thought KeepassXC works like other password managers with a network socket. Huh, I’ll have to poke around.

      I have yet to try the KeepassXC extension on Windows and I’m tempted to install Waterfox directly on my Linux device via tar file to see if that fixes things.

      Edit: Keepass official documentation states that flatpaks are not support at all. Installed Waterfox via it’s tar file and works as expected after following the instructions here.

      TL;DR: within KeepassXC, go to Tools > Settings. Then go down to “Browser Integration”. Select the “Advanced” tab and set the config location to ~/.waterfox/native-messaging-hosts.