mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3262] keepassxc: cannot access NTFS mountpoints in /storage (private-etc) #2047
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#2047
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 @freerunner on GitHub (Mar 2, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3262
Profile issue with: keepassxc (maybe others as well, just started setting up Firejail)
Runs with --noprofile option: yes
Linux distribution: KDE Neon User Edition (Ubuntu 18.04)
Firejail version: 0.9.62 (from ppa)
My external NTFS data mount points, located in /storage are not visible within the jailed keepassxc.
However, if I comment the line
private-etc alternatives,fonts,ld.so.cache,machine-idthey're accessible again.
Mount options for the drives in fstab:
UUID=[cut] /storage/Data ntfs defaults,umask=007,uid=1000,gid=100,noatime,big_writes 0 0/storage/Data is whitelisted in whitelist-common.local as well.
Can anybody help?
@rusty-snake commented on GitHub (Mar 2, 2020):
whitelisting isn't supported for /storage, this hasn't any effect.
Can you run
firejail --build keepassxc | grep private-etcand post the output (should only oneprivate-etcline).@freerunner commented on GitHub (Mar 2, 2020):
Sure.
This is with a stock profile:
andy@X570DESKTOP:/etc/firejail$ firejail --build keepassxc | grep private-etcprivate-etc drirc,fonts,gcrypt,kde5rc,login.defs,passwd,Wicked: After running
firejail --build keepassxc | grep private-etcI can see all my mount points in /storage. If I simply run keepassxc from terminal they're gone.edit: reformat code blocks
@freerunner commented on GitHub (Mar 3, 2020):
I'm back. :)
Okay, after adding the items to private-etc in the profile, there are more detailed error messages:
https://pastebin.com/RgT3sX7q
@ghost commented on GitHub (Mar 3, 2020):
That is expected behaviour. The
--buildoption creates a volatile profile, meaning that will be gone (not saved to disk) the next time you run without the '--build' parameter. We'll see what we can do to fix the default keepassxc profile. But for now you can use--build=keepassxc.profile, which will save keepassxc.profile to your ${HOME}/.config/firejail directory. Once that is done, you should be able to see your external NTFS data mount points when simply running 'keepassxc' or 'firejail /usr/bin/keepassxc' like before.@rusty-snake commented on GitHub (Mar 3, 2020):
@freerunner is there anything in the journal/syslog.
@freerunner commented on GitHub (Mar 3, 2020):
Aha. I'm slowly beginning to understand. The --build parameter does not interfere with the normal exectution of the program, instead starts to monitor the behavior. Then a profile is created after the application has been closed. Is this correct?
Okay, created a custom profile. When run with it, firejail reports an invalid whitelisted filename path.
-> whitelist /var/run/samba/gencache_notrans.tdb
After removing that line, keepassxc runs, but all NTFS mountpoints are gone again.
This is the custom profile: https://pastebin.com/LW8KmVcP
This is the output in stderr after closing the app:
@rusty-snake
With the custom profile, syslog is clean from messages.
This is a recent syslog output with a stock profile:
https://pastebin.com/DdzZPRPH
@rusty-snake commented on GitHub (Apr 1, 2020):
still need help?
@rusty-snake commented on GitHub (Jun 4, 2020):
I'm closing here due to inactivity, please fell free to reopen if you still have this issue.