Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Firefox flatpak] key exchange failed #804

Closed
vasyugan opened this issue Mar 11, 2020 · 3 comments
Closed

[Firefox flatpak] key exchange failed #804

vasyugan opened this issue Mar 11, 2020 · 3 comments
Labels
software packages & sandboxes AppImage, Snap, Flatpack etc. wontfix

Comments

@vasyugan
Copy link

vasyugan commented Mar 11, 2020

Expected Behavior

The keepassxc extension should just work (tm) with flatpak packaged firefox as with native firefox builds

Current Behavior

I just installed the official firefox flatpak from flathub

flatpak install https://flathub.org/beta-repo/appstream/org.mozilla.firefox.flatpakref

I see that it can't connect to my keepassxc. The debugger says:

Error 5: Die Verbindung zu KeePassXC ist nicht möglich. Überprüfen Sie, ob die Browser-Integration in den KeePassXC-Einstellungen aktiviert ist. keepass.js:1062:13
Connecting to native messaging host org.keepassxc.keepassxc_browser keepass.js:979:13
Failed to connect: Unknown error keepass.js:949:13
Error: No content script available for this tab. keepass.js:1180:25
Error 9: Schlüsselaustausch war nicht erfolgreich. keepass.js:1062:13

Debug info

KeePassXC -2.5.3
KeePassXC-Browser - 1.5.4
Operating system: Linux
Browser: Firefox (official flatpak from flathub-beta)

@varjolintu varjolintu added software packages & sandboxes AppImage, Snap, Flatpack etc. wontfix labels Mar 11, 2020
@varjolintu
Copy link
Member

AFAIK, Native Messaging doesn't work with flatpak or snap. KeePassXC can be installed as a snap or flatpak though, but your browser must be installed via the package manager.

@vasyugan
Copy link
Author

It seems, this needs a change in XDG desktop portal and Firefox, see this comment by a mozilla developer .

@droidmonkey
Copy link
Member

droidmonkey commented Mar 11, 2020

That's a great response! I wish the browsers would come up with a standard secure communication protocol that can broker a trust relationship with a native application. Stdio is great, but it carries with it accessibility requirements. Using dbus or a more portable (between operating systems) broker would be much preferred all around.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
software packages & sandboxes AppImage, Snap, Flatpack etc. wontfix
Projects
None yet
Development

No branches or pull requests

3 participants