KeepassXC-Browser doesn't work out of the box

Support
1

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).

2

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.

3

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?

4

This is documented.

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

1 Like