mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2154] Split up disable-mnt #1462
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#1462
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 @chiraag-nataraj on GitHub (Oct 9, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2154
We should split
disable-mntinto two different directives (disable-mntanddisable-media) to make things more granular.@chiraag-nataraj commented on GitHub (Oct 9, 2018):
Alternate proposal by @smitsohu: Turn
disable-mntinto a set of ordinaryblacklistcommands, which can be overridden as usual withnoblacklist.@smitsohu commented on GitHub (Oct 9, 2018):
Adding some advertisement for my own proposal: I doesn't change the meaning of an existing option and hence doesn't create a need to update existing profiles.
Also I recall people actually trying to noblacklist /media or /mnt in order to get their setup running, and posting to the bug tracker because that didn't work.
@startx2017 commented on GitHub (Oct 9, 2018):
We have disable-mnt in firetools GUI. Replacing it with blacklists in profile files should be fine.
@Fred-Barclay commented on GitHub (Oct 10, 2018):
@smitsohu Would
disable-mntjust blacklist /mnt as a whole?@smitsohu commented on GitHub (Oct 10, 2018):
@Fred-Barclay Like it does currently, yes.
@Vincent43 commented on GitHub (Oct 10, 2018):
I think splitting
disable-mediawill only add maintenance burden as there will be yet another option to add to each profile. Changing it behavior to work as--blacklist=/media--blacklist=/run/media--blacklist=/mntwhich will be overridable by--noblacklistsounds much better.