mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #5694] Fvwm "Restart" creates directory outside --private or --overlay-tmpfs sandbox? #3068
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#3068
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 @laniakea64 on GitHub (Feb 27, 2023).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5694
Environment
Xubuntu 22.04
firejail self build from
4201eb4f7afirejail X11 sandboxing uses Xephyr on this system.
Steps to reproduce
~/.fvwmdirectory, runconfirm that
~/.fvwmexists inside the sandbox but not outside itopen Fvwm menu > Restart
Expected results: Fvwm either restarts or quits, and the real filesystem should not be modified.
Actual results:
Fvwm quits. An empty directory
~/.fvwmis created on the real filesystem, outside the sandbox. Owner & group are both my user, and mode is 0755.Wondered if I might be missing something in the sandboxing, but same thing happens with
firejail --x11 --private --noprofile --dbus-user=none --dbus-system=none --net=none --caps.drop=all --seccomp fvwm2.Same results occur with
--overlay-tmpfs(with modified firejail build to allow this) instead of using--private.Using Fvwm menu > Quit instead of Restart does not reproduce this behavior.