mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #940] Implement SandboxIE features #640
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#640
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 @KOLANICH on GitHub (Nov 26, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/940
SandboxIE is a sandbox for Windows. It has some features not present in firejail like IPC isolation (if you start FireFox in a sandbox it starts in sandbox without respect to FF out of sandbox). The processes in a sandbox don't see the processes in another sandboxes and out of sandboxes). There is a need to find out what is missing in firejail and implement it.
@valoq commented on GitHub (Nov 26, 2016):
Firejail has the ipc-namespace option to create a new ipc namespace with complete isolation.
Sandboxie is a closed source application claiming to sandbox other processes. It‘s hard to tell how useful that sandbox really is and what it really does, I wouldn‘t trust that software.
@KOLANICH commented on GitHub (Nov 26, 2016):
I understand that. I just wonder if it is at least as secure to run malware not using privilege escalation exploits in firejail as it is in SandboxIE, assuming that there is no backdoors and the existing features are implemented correctly.
@netblue30 commented on GitHub (Nov 27, 2016):
This is done by default.