mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1556] Running Virtualbox with seccomp? #1035
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#1035
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 @Futureknows on GitHub (Sep 17, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1556
Is it possible to firejail Virtualbox with seccomp or namespace?
@netblue30 commented on GitHub (Sep 18, 2017):
Virtualbox needs to raise privileges in order to start or communicate with its own kernel modules. Seccomp will kill it immediately. Namespaces are working fine and are currently enabled. Also, the home directory is whitelisted, so you have access only to ~/VirtualBox and ~/Downloads directory.