mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #203] Question about shell=none #140
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#140
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 @nick75e on GitHub (Dec 28, 2015).
Original GitHub issue: https://github.com/netblue30/firejail/issues/203
Hi!
With versions 0.9.32 and earlier, when I wanted to join an existing firejail session with
shell none, it would tell me that it's already in use and then deny access. But with 0.9.34, I can join in.Is it on purpose?
Thanks.
@netblue30 commented on GitHub (Dec 29, 2015):
Yes, it will join the sandbox if /bin/bash or /bin/sh is available inside the sandbox. The idea is to provide a way to modify a running sandbox.
@nick75e commented on GitHub (Dec 29, 2015):
Then what does
shell noneactually do?I thought it was to prevent apps from accessing the shell within the sandbox.
PS: Sorry for the stupid questions but I'm a little lost here
@netblue30 commented on GitHub (Dec 29, 2015):
It starts the application directly, without a shell. However, --join creates a new shell in the sandbox. The shell is running in parallel with your application. Your application still runs outside the shell, but it could create a shell of its own.
@nick75e commented on GitHub (Dec 29, 2015):
Now I understand!
Thanks for answering and the release of 0.9.36 btw.