mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1071] Per directory overlayfs filesystems? #727
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#727
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 @talwrii on GitHub (Jan 24, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1071
I'm happily misusing firejail to sandbox zsh.
One use case is distrusting code that I clone off the internet. For this purpose I create a firejail where
One problem I get is that some of my zsh plugins want to write to files. An ideal solution here would be give them an overlayfs to write into. However, I don't want an overlayfs everywhere (my experience profiles is that I tend to try to use shells for things that I'm not meant to unless there's something to stop me, so I would happily try to make changes to the overlayfs shell that then get lost).
One solution is the have something like
--overlay-dir=blahso that I can turn overlays on and off in a fine-grained fashion.Opinions?
@netblue30 commented on GitHub (Jan 25, 2017):
--overlay-dir will be!