mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #738] Consider improving the documentation of --whitelist #500
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#500
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 @jody-frankowski on GitHub (Aug 21, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/738
I have just noticed that when you add the
--whitelistargument firejail mounts a new /home and a new /root (otherwise it doesn't by default).I was having a hard time understanding how this was happening in my profile, and i think this might deserver bigger flags :-)
Edit:
I have noticed the documentation for
whitelistin man firejail-profile(5) documents this properly, but I think the issue is still on point because the documentation for--whitelistin man firejail(1) isn't the same.@netblue30 commented on GitHub (Aug 22, 2016):
Fixed, thanks.