mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2645] firefox passf plugin not working #1669
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#1669
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 @maxodoble on GitHub (Apr 12, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2645
hi,
when using firejail with firefox on arch the passff extension stops working. passff (https://github.com/passff/passff) uses a native messaging host app to communicate with the pass passwordstore. the native messaging app is a python3 app (https://github.com/passff/passff-host).
what can i do get this browser plugin working when using firejail?
thanks,
Max
@ghost commented on GitHub (Apr 12, 2019):
Due to the complexities of web browsers, firejail has split-up the firefox profile layout. You can use an override file
firefox-common.local, either in /etc/firejail or ~/.config/firejail with the following content:The included
firefox-common-addons.incunblocks python3 in a comment relating to GNOME Shell integration (chrome-gnome-shell), but it will work for passff too:Besides that you'll need to make sure additional paths relating to pass/passff are whitelisted.
@maxodoble commented on GitHub (Apr 12, 2019):
Thanks much,
with your help i am one step further: passff is getting the infos from the passwordstore now correctly.
but now i am stuck at the next step: pinentry:
when trying to fill out a form-entry from passff i am getting no more popup for the pwd to the private key which is necessary for getting the credentials out of the passwordstore. so passf stops here with "no gpg key..."
any idea for that as well? (whitelist pinentry or something?)
Cheers,
Max
@ghost commented on GitHub (Apr 12, 2019):
@maxodoble The plot thickens 😄 ... Looks like you'll need to whitelist access to ${HOME}/.gnupg for passff too. PassFF needs a GUI pinentry program (see https://github.com/passff/passff#troubleshooting). On Arch these are included in the pinentry package, but you might want to check what you have configured in ~/.gnupg/gpg-agent.conf. More info on that on the Arch Wiki.
Now I remember why I stopped using pass/passff with a firejailed firefox, it's complicated and I never bothered to get it all working correctly without loosening the profile too much. Best of luck, interested in your experiences to get this combo working.
@maxodoble commented on GitHub (Apr 12, 2019):
So i did whitelist ~/.gnupg but i am stuck at the pinentry problem.
tried with
noblacklist /usr/bin/pinentry-gnome3but i still can't get the pinentry popup to show up.so, if anybody has an idea, i'd appreciate it :-)
@ghost commented on GitHub (Apr 13, 2019):
@maxodoble Have you tried
whitelist ${PATH}/pinentry-gnome3yet? Also, try to experiment by addingignore nodbus, D-Bus is quite notorious for breaking functionalities.@maxodoble commented on GitHub (Apr 14, 2019):
tried now:
whitelist ${PATH}/pinentry-gnome3this gives:
Error: invalid whitelist path ${PATH}/pinentry-gnome3adding
ignore nodbusalone (without pinentry whitelist), also doesn't seem to work.i think i am at a point now, where it's not worth the hassle ;-)
Thanks though very much for your help and input, at least i learned some new stuff along the way :-)
All the best,
Max
@chiraag-nataraj commented on GitHub (Apr 26, 2019):
Hey @maxodoble! It seems like it's reasonable to go ahead and close this due to your last comment, but please feel free to re-open this if you have more questions or have updates and manage to get it working!