mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #280] read-only whitelists #193
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#193
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 @netblue30 on GitHub (Feb 8, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/280
From wordpress:
Is there any chance for read-only whitelisting? I would like to whitelist a certain file, but also to make sure the program can’t change that file. Right now, I try to make a copy of that file to a temporary private home, but some files are too large to do that with.
@manevich commented on GitHub (Feb 8, 2016):
Unable to find original discussion on wordpress, so I may miss something,
but
firejail --whitelist=some-file --read-only=some-filesolves this problem, isn't it?This can be improved a bit, by checking if file is also in read-only list when white-listing so it's mounted only once:
@netblue30 commented on GitHub (Feb 9, 2016):
The solution is to both --whitelist and --read-only. It is already implemented in 0.9.38