KeepassXC-Browser doesn't work out of the box

KeepassXC-Browser is blocked by apparmor in Tor Browser.

This seems stupid especially since KeepassXC comes by default with Whonix.

I eventually got it working but it would be great if better minds than I could make it work without needing scary manual changes from the defaults.

I wrote about what I had to do to get it working at github Kicksecure apparmor-profile-torbrowser issues 14 (sorry not allowed to post URLs - guess I’m too new).

and it shouldnt work, integrating x add-on into TB will give changes that will effect the browser fingerprint thus it wont be support by default.

you can disable apparmor if that annoys, but there should be no upstream behavior change.

I just allowed the particular keepassxc-proxy executable to run in apparmor, so I didn’t disable apparmor completely.

Wait… so javascript can detect what plugins there are installed?

This is documented.

http://www.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/wiki/Tor_Browser#Non-default_Add-on_Risks

1 Like

Keepassxc doesnt connect with torbrowser extension.

Working with whonix-17. All updated. Fresh install of keepassxc (sudo apt install keepassxc)
TorBrowser is also updated (13.0.14 (based on Mozilla Firefox 115.10.0esr).

Browser Integration is activated
Browser extension is installed

I’ve checked the troubleshooting guide of keepassxc but I dont know how to proceed further. So far I’ve done:
Troubleshooting point 1 done: Checked for the .json file and path-> all good.
Troubleshooting point 2 done: Checked for the .json path to keepassxs-proxy → all good

Troubleshooting point 3:
I did: “Use the following command: sudo strace -f -p $(pgrep firefox) 2>&1 | grep keepass”

Result:

[pid 18564] openat(AT_FDCWD, "/home/user/.tb/tor-browser/Browser/TorBrowser/Data/Browser/.mozilla/native-messaging-hosts/org.keepassxc.keepassxc_browser.json", O_RDONLY <unfinished ...>
[pid 18564] stat("/usr/bin/keepassxc-proxy",  <unfinished ...>
[pid 18564] stat("/usr/bin/keepassxc-proxy",  <unfinished ...>
[pid 18564] stat("/usr/bin/keepassxc-proxy",  <unfinished ...>
[pid 18564] stat("/usr/bin/keepassxc-proxy",  <unfinished ...>
[pid 18564] stat("/usr/bin/keepassxc-proxy",  <unfinished ...>
[pid 19060] execve("/usr/bin/keepassxc-proxy", ["/usr/bin/keepassxc-proxy", "/home/user/.tb/tor-browser/Brows"..., "keepassxc-browser@keepassxc.org"], 0x7ec6ea877800 /* 79 vars */ <unfinished ...>

Then I did: ps aux | grep keepassxc-proxy
Result:
user 19618 0.0 0.0 6468 2048 pts/2 S+ 13:47 0:00 grep --color=auto keepassxc-proxy

Would be great if someone can help me out here

Not a Whonix specific issue?

Try Linux (Debian) + Tor Browser (TB) + KeePassXC.

Needs to be resolved as per:

By asking TB and/or KeePassXC.

Simple answer: KeePassXC extension not supported

1 Like

I did what I had to do from the blog, it was already installed. the browser extension gives an error.

keepassxc yubikey-personalization yubikey-personalization-gui

it was already installed but when I tried it anyway it gave me an error as not found.

This fix CLICK

Extension Cannot Connect to KeePassXC - "Key Exchange Was Not Successful" · Issue #1399 · keepassxreboot/keepassxc-browser · GitHub is interesting.

Could you please contribute Whonix specific documentation here?
KeePassXC Browser Extension