mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3200] firefox: keepassxc browser addon: Key exchange not successful #1999
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1999
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ericschdt on GitHub (Feb 3, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3200
If I start the Firefox with Firejail and try to connect the KeepassXC browser addon to the KeepassXC app, the addon says "key exchange unsuccessfull".
If however the Firefox is started outside of Firejail, everything is fine.
Any idea?
Additional notes
The KDEconnect browser addon runs fine with default settings + the ignore nodebus "trick".
System
FF 72.0.2
firejail 0.9.62
KeePassXC 2.5.2
KeepassXC Browser Addon 1.5.4
Archlinux
@ghost commented on GitHub (Feb 3, 2020):
@ericschdt I've installed keepassxc on Arch together with its browser addon and did some testing. With the firejail profiles from current git (which is what I use daily) I could reproduce. Editing the firejail options didn't do much in this context. And then I noticed this:
On my system /usr/local/bin/keepassxc-proxy does not exist, /usr/bin/keepassxc-proxy does. As soon as I edited in the correct path and restarted Firefox the problem was gone. This was my first time ever using KeepassXC, so this might be beginners luck :)
@ericschdt commented on GitHub (Feb 4, 2020):
That's good, however unfortunately
both exist on my system:
and
did not help me. :-(
I also found out that the KeepassXC browser addon always says "unsuccessful key exchange", no matter if KeepassXC is running and/or unlocked in the background.
Definitely!
@ericschdt commented on GitHub (Feb 4, 2020):
I replaced the profiles with their git counterparts and now it works! :)
@ericschdt commented on GitHub (Feb 5, 2020):
Okay, now it no longer works. I don't know what's happening and I will have to investigate more later.
@ghost commented on GitHub (Feb 6, 2020):
@ericschdt Feel free to re-open this if after additional investigation the issue persists.
@ericschdt commented on GitHub (Feb 9, 2020):
I could resolve the issue by adding
keepassxc-proxyto the private-bin line in thefirefox.profilefile:Alternatively one could have uncommented
include firefox-common-addons.incinfirefox-common.profileAND
private-bin keepassxc-proxyinfirefox-common-addons.inc@saddy001 commented on GitHub (Oct 17, 2021):
For me this worked:
Then restart Firefox. Also see #3952
@rusty-snake commented on GitHub (Oct 17, 2021):
Also see https://github.com/keepassxreboot/keepassxc/discussions/6741#discussioncomment-1154242.