mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1001] blacklist /mnt by default #684
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#684
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 @thewisenerd on GitHub (Dec 23, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1001
/mntdirectory is not blacklisted by default and this usually has mounted filesystems. should firejail consider blacklisting it by default, and have applications request whitelisting it if (and only if) necessary?@netblue30 commented on GitHub (Dec 27, 2016):
No, we cannot do it. We can only blacklist/whitelist by default directories and files we know about. For example we blacklist /boot because we can access it by default and some of the files there are very bad. For /mnt or /media is different, the user can have mounted there anything.
I'll add an option in /etc/firejail/firejail.config to disable globally /mnt, /media and /run/media.
@netblue30 commented on GitHub (Mar 10, 2017):
Added "disable-mnt yes/no" config option in /etc/firejail/firejail.config file.