mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1073] Ability to disable process namespaces #731
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#731
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 @talwrii on GitHub (Jan 24, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1073
I'm misusing firejail to jail zsh. It would quite nice if i could get a zsh that lives in the the global process namespace so that ps works etc.
@netblue30 commented on GitHub (Jan 25, 2017):
Not possible, all the code expects a process namespace.
@talwrii commented on GitHub (Jan 25, 2017):
Cool cool.
If you think something like this feature is worth having (which is far from clear), one approach might be to steal the process namespace from /proc/1/ns/pid in the outer scope, which I presume is the default namespace for the machine.
@valoq commented on GitHub (Jan 27, 2017):
You can probably get the process list by using dbus and systemd to start a process outside the sandbox.
If the dbus socket in /run/user/UID/bus is available, it presents a way to escape the sandbox.