it does not have any generic access to the file system (it uses portals). Now why it does not work if Firefox is installed as a flatpak: The very good official Firefox flatpak by Mozilla really does have few permissions for being a browser.That is, so far, why Firefox installed on the host does work….Flathub KeePassXC has a patch that allows the keepassxc-proxy to be started via flatpak run, i.e.The only thing it possibly needs to do is get into the KeePassXC flatpak. If Firefox is not sandboxed, that proxy can start as usual.KeePassXC-Browser) and tries to listen on that socket to find messages. 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. And, so, yes, I agree, I wouldn't trust any password manager to auto-fill credentials.If KeePassXC is sandboxed in a Flatpak, browsers can only access it, if they are not sandboxed, i.e. However, the convenience (tempered with the manual clicking on the icon) is preferred. Yes, I can (and now must) copy and paste the credentials from KeepassXC. But, it doesn't auto-fill the credentials, this is an option in KeepassXC that I don't (and wouldn't) use. They must be acknowledged beforehand as appropriate for the URL (and this option can be saved). The credentials that will be filled (on click) can be verified. I must manually click an icon that shows on the webpage normally, and KeepassXC will fill-in the credentials. KeepassXC handles this like a charm.Īs regards "automatic signin". RouterOS doesn't work similarly: there is a webpage with fields to be filled in. I have seen one site where the entry box isn't "open" until you click in the box, and this stumps KeepassXC. I don't have any other websites that work exactly this way, so I can't answer whether KeepassXC responds similarly. Yes, it is the way the pop-up screen works (which I don't fully understand).
0 kommentar(er)
