wile_e8 , 8 months ago

OK, so I looked though my browser history, and here are some relevant pages I found:

• keepassxc-browser Issue 1267
• keepassxc-browser Issue 1631
• keepassxc-browser Issue 1783
• browserpass-native Issue 93

I don’t remember how much I used each one, but eventually I pieced together enough information information to get the Browserpass extension working in the Google Chrome flatpak. But three of those links are KeePassXC, which should be useful for adapting this for your use.

The main file that was having problems was the Browserpass Native Messaging Hosts file in my config directory for the Chrome flatpak, ~/.var/app/com.google.Chrome/config/google-chrome/NativeMessagingHosts/com.github.browserpass.native.json. Originally it was a symlink to a file at /usr/lib/browserpass/hosts/chromium/com.github.browserpass.native.json:

<span style="color:#323232;">{
</span><span style="color:#323232;">    "name": "com.github.browserpass.native",
</span><span style="color:#323232;">    "description": "Browserpass native component for the Chromium extension",
</span><span style="color:#323232;">    "path": "/usr/bin/browserpass-linux64",
</span><span style="color:#323232;">    "type": "stdio",
</span><span style="color:#323232;">    "allowed_origins": [
</span><span style="color:#323232;">        "chrome-extension://naepdomgkenhinolocfifgehidddafch/"
</span><span style="color:#323232;">    ]
</span><span style="color:#323232;">}
</span>

The call to /usr/bin/browserpass-linux64 did not see to work for me, so I ended up making a copy of the file in the NativeMessagingHosts directory and modified it to point to a script in my home mount:

<span style="color:#323232;">wile_e8 NativeMessagingHosts $ diff com.github.browserpass.native.json.orig com.github.browserpass.native.json
</span><span style="color:#323232;">4c4
</span><span style="color:#323232;">&lt;     "path": "/usr/bin/browserpass-linux64",
</span><span style="color:#323232;">---
</span><span style="color:#323232;">>     "path": "/home/wile_e8/.config/browserpass/browserpass.sh",
</span><span style="color:#323232;">
</span>

I don’t remember why I picked to do it inside the ~/.config directory, but it worked so I left it. And here is the script I put at ~/.config/browerpass/browserpass.sh:

<span style="color:#323232;">#!/bin/sh
</span><span style="color:#323232;">cd ~
</span><span style="color:#323232;">/usr/bin/flatpak-spawn --host /usr/bin/browserpass-linux64 2>/tmp/error.log
</span>

I don’t remember how I came up with that script, it must be somewhere in the four links at the top.

Finally, I needed to use Flatseal to allow access to the script. In the Google Chrome settings, under “Filesystem->Other files”, I added an entry saying ~/.config/browserpass:ro. Also modified from the default in Flatseal, I have “Filesystem->All user files” enabled, along with “Socket->D-Bus session bus” and “Socket->D-Bus system bus”. I don’t know how necessary the last three are, but I’m not messing with it now that I have it working.

So, that’s what I did to get the Browserpass extension working in the Google Chrome flatpak. You’ll have to modify some things to get it working for KeePassXC, or for Firefox. But that general pattern should work.