mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1603] Allow nesting of sandboxes #1070
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#1070
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 @marcthe12 on GitHub (Oct 13, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1603
I believe that we should be able to nest sandboxes. This could allow sandbox of more lower programs
@SkewedZeppelin commented on GitHub (Oct 13, 2017):
The permissions required to create the nested sandboxes are dropped upon creating the initial sandbox. Keeping those permissions would allow the programs inside the sandbox to very easily escape.
See https://github.com/netblue30/firejail/issues/1256#issuecomment-298379932