![]() keepassxc-proxy is started – via native messaging – by the browser (triggered by the add-on i.e. KeePassXC creates an UNIX socket in $XDG_RUNTIME_DIR/kpxc_server for applications to listen too.But for the curious, I’ll explain the problems we face: If you just want the solution, you can skip this part. This problem is shown in various GitHub issues: flathub/#29, keepassxreboot/keepassxc#2656, xhorak/firefox-devedition-flatpak#92, keepassxreboot/keepassxc-browser#297, flathub/#13, xhorak/firefox-devedition-flatpak#92, this Bugzilla bug, not to mention the many dupes like keepassxreboot/keepassxc-browser#297, keepassxreboot/keepassxc-browser#276, keepassxreboot/keepassxc-browser#102 etc. I show a workaround that makes it possible to use both configurations. this does not: Firefox (sandboxed), KeePassXC (host or sandboxed, does not matter).this should work out-of-the box: Firefox (host-installed), KeePassXC (flatpak from flathub).Firefox, and KeePassXC – or at least the browser and installing KeePassXC natively, which you’d actually want for security reasons – is not possible. ![]() installed as an deb/rpm package or similar on the host. If KeePassXC is sandboxed in a Flatpak, browsers can only access it, if they are not sandboxed, i.e. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |