mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #6100] keepassxc: cannot save database #3180
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#3180
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 @oknyshuk on GitHub (Nov 23, 2023).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6100
Description
Hardened and sandboxed KeePassXC can't save the password database.
Steps to Reproduce
firejail keepassxcExpected behavior
I expected KeePassXC to save the file without troble, especially since I have
ignore private-tmpin my keepassxc.localActual behavior
I have an error.
Behavior without a profile
Everything works fine.
Additional context
~/.config/firejail/keepassxc.local:
Screenshot:

Related KeePassXC settings:

Environment
3c303ab1dc)Checklist
/usr/bin/vlc) "fixes" it).https://github.com/netblue30/firejail/issues/1139)browser-allow-drm yes/browser-disable-u2f noinfirejail.configto allow DRM/U2F in browsers.--profile=PROFILENAMEto set the right profile. (Only relevant for AppImages)Log
Output of
firejail keepassxcOutput of
firejail --debug keepassxchttps://gist.github.com/k1gen/bc4feee5e5e3a8eba74eee64909e626e
@rusty-snake commented on GitHub (Nov 23, 2023):
Play with "Use alternative saving method" OR whitelist the folder containing your kdbx.
@oknyshuk commented on GitHub (Nov 23, 2023):
I get this after disabling "Use alternative saving method":

The "Directly write to database file (dangerous)" option works, but if we can work out this bug and not use - I'd like to do that.
@rusty-snake commented on GitHub (Nov 24, 2023):
If you do not want direct writes, you have to whitelist the directory in which your kdbx resides rather than the kdbx file itself.
@oknyshuk commented on GitHub (Nov 24, 2023):
thanks, that works!