mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #838] Whitelist only specified input files #569
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#569
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 @valoq on GitHub (Oct 6, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/838
Is there a way to whitelist only those file that are used as arguments for the command?
Like: "firejail programm fileToOpen"
That way it would be possible to block access to the complete filesystem except for the specified file.
@manevich commented on GitHub (Oct 6, 2016):
Currently no, but I am working on this now. I will send pull request when I am done (Friday or Sunday I think).
@valoq commented on GitHub (Oct 6, 2016):
Great, thanks
@valoq commented on GitHub (Oct 26, 2016):
Any updates on this?
@manevich commented on GitHub (Oct 26, 2016):
Sorry, I have had no spare time this month.
Putting current version here.
It's seems working, but still needs to be cleaned, tested thoughtfully, and documented.
@chiraag-nataraj commented on GitHub (Jul 25, 2018):
The easiest way (currently) is to setup a wrapper script. I might look into doing this if @manevich didn't merge their changes.
@chiraag-nataraj commented on GitHub (Jul 25, 2018):
I think the tricky (with regards to security) part of this is that we'd have to (safely) parse the child program's argument list, which brings with it a whole host of issues (potentially).