mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #583] How to hide entire home directory except number of subdirectories #409
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#409
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 @weeshy on GitHub (Jun 19, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/583
I'd like to hide from an application entire ${HOME} directory, but allow access to number of working directories, that lies inside the home, like ${HOME}/MyWorkDir and ${HOME}/MyCacheDir.
I've tried --private with --whitelist, but whitelist was ignored, I've got an empty home directory. I give another try to --blacklist=${HOME} and --whitelist=${HOME}/MyWorkDir, but whitelist was ignored again: I could not access specified directory that is inside a blacklisted path.
So, how it is supposed to configure firejail in that use case? Some of directories should be whitelisted as read-only weights a lot, so I could just copy them to another directory and go the way of full chroot.
@netblue30 commented on GitHub (Jun 19, 2016):
--whitelist does all the job by default. You don't need to add --blacklist or --private:
@weeshy commented on GitHub (Jun 19, 2016):
That works fine, thanks for the information