mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #239] Re-attach to an overlay after the sandbox is closed #171
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#171
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 (Jan 20, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/239
From wordpress:
Hi,
Is it possible to re-attach to an overlay after the sandbox is closed? Now, a new overlay is always created, but I would like to continue where I left of.
Thanks,
eli
@dshmgh commented on GitHub (Feb 13, 2016):
I have experimented with the overlayfs mount and if I manually remount over a previous sandbox, the merge appears to work properly. If an option is added --reoverlay and then that creates the /home/$USER/.firejail/persist dir and that dir is used instead of /home/$USER/.firejail/$PID for the overlay then I think this enhancement would work. But does this reuse of a previous sandbox somewhat defeat the purpose of using firejail?
I'll get some code for this change to you at some point.
@netblue30 commented on GitHub (Feb 13, 2016):
I'm really interested in this feature, so if you send me some code I'll merge it in. The reason I've been sleeping on it is remounting the overlay is a huge security problem. For example, in the overlay you modify /etc/shadow, then start firejail and become root. I'll have to restrict --reoverlay to root user.
@Sidnioulz commented on GitHub (Feb 21, 2016):
@netblue30 would the issue exist if user namespaces were in place?
@netblue30 commented on GitHub (Feb 21, 2016):
Overlayfs and user namespace should be two different subsystems.
@netblue30 commented on GitHub (Sep 6, 2016):
Implemented in 0.9.42~rc2