Without the flatpak sandbox, Firefox has access to everything in $XDG_RUNTIME_DIR as everything in the runtime directory is owned by the same user running Firefox. Due to sandboxing, the flatpak version of Firefox has two problems to solve before it can communicate with KeePassXC: socket access and socket communication. The browser extension then uses Native Messaging to run a binary that communicates with the socket. Newer versions use $XDG_RUNTIME_DIR/app//Īssuming you have an up-to-date flatpak, the socket should be located at the newer path.Older versions of KeePassXC use $XDG_RUNTIME_DIR/kpxc_server.This is a common method for two different pieces of software to communicate and for our purposes we view it a simple file that we need to read and write to. KeePassXC uses a socket to communicate with browser extensions which is located at one of two locations. Both of these are explained, however, and can be modified to suit one’s needs. The only differences would be in the location of the socket (for non-flatpak versions of KeePassXC) and the location of the home directory for the. It should work on other distributions, especially if when using flatpak versions of both Firefox and KeePassXC, but it has only been verified on Fedora 36/37. This guide was written for and verified with Fedora 36 Silverblue.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |