mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3185] allowing fscrypt files #1993
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#1993
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 @reinerh on GitHub (Jan 25, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3185
A Debian user reported probems with whitelisting and accessing fscrypt-related files from within firejail.
Especially /home/.fscrypt seems to be a problem, because only the user's home directory is available in /home, not any other directories/files.
Does anyone have an idea how this could be fixed?
@rusty-snake commented on GitHub (Jan 25, 2020):
unsure whether helpful
@reinerh commented on GitHub (Jan 25, 2020):
Thanks, that works for me. I'll forward your suggestion and ask if that solves their problem.
@reinerh commented on GitHub (Jan 25, 2020):
It looks like they are also using
--private, and it's currently not possible to combine this with--allusers(Warning: allusers option disabled by private or whitelist option).Do you know of any workaround for that?
@rusty-snake commented on GitHub (Jan 25, 2020):
firejail --allusers --private->Warning: allusers option disabled by private or whitelist optionfirejail --allusers --private=/some/where-> worksNOTE: $private_home is visible for other programs (except
firejail --private-tmp).@reinerh commented on GitHub (Jan 31, 2020):
Looks like the problem is actually with
--whitelist, not with--private:With
--allusersits not possible to see the hidden files in /home.Do you have another idea how to get access there with e.g. the firefox profile?