github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #858] What does "shell none" do #583

New issue

Closed

opened 2026-05-05 06:13:13 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 06:13:13 -06:00

Owner

Originally created by @vismir2 on GitHub (Oct 15, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/858

According to the Manpage:
--shell=none
Run the program directly, without a user shell.

          Example:
          $ firejail --shell=none script.sh

This doesn't really explain much. What is it for. Why should or shouldn't I use it?

Originally created by @vismir2 on GitHub (Oct 15, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/858 According to the Manpage: --shell=none Run the program directly, without a user shell. ``` Example: $ firejail --shell=none script.sh ``` This doesn't really explain much. What is it for. Why should or shouldn't I use it?

gitea-mirror

2026-05-05 06:13:13 -06:00

closed this issue
added the
information_old
label

gitea-mirror commented

2026-05-05 06:13:19 -06:00

Author

Owner

@netblue30 commented on GitHub (Oct 16, 2016):

By default it runs the program in a new shell. For example, if you start "firejail firefox", after setting the sandbox it actually runs "/bin/bash -c firefox". --shell=none runs the program directly.

@netblue30 commented on GitHub (Oct 16, 2016): By default it runs the program in a new shell. For example, if you start "firejail firefox", after setting the sandbox it actually runs "/bin/bash -c firefox". --shell=none runs the program directly.

gitea-mirror commented

2026-05-05 06:13:22 -06:00

Author

Owner

@vismir2 commented on GitHub (Oct 16, 2016):

When do I need that option?
Are there any security implications with that option?

@vismir2 commented on GitHub (Oct 16, 2016): When do I need that option? Are there any security implications with that option?

gitea-mirror commented

2026-05-05 06:13:26 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Oct 16, 2016):

It's useful if you want to use --private-bin to limit the binaries available - not having access to a shell program if the program is hacked is a Really Good Thing (TM) 😉

@chiraag-nataraj commented on GitHub (Oct 16, 2016): It's useful if you want to use `--private-bin` to limit the binaries available - not having access to a shell program if the program is hacked is a Really Good Thing (TM) :wink:

gitea-mirror commented

2026-05-05 06:13:29 -06:00

Author

Owner

@netblue30 commented on GitHub (Oct 17, 2016):

Yes, is relevant for --private-bin. I don't think there are any security implications.

@netblue30 commented on GitHub (Oct 17, 2016): Yes, is relevant for --private-bin. I don't think there are any security implications.

gitea-mirror referenced this issue

2026-05-05 08:05:57 -06:00

[GH-ISSUE #2114] Hiding HOME with --whitelist: cannot open directory '.' #1432

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#583

No description provided.

Rows
Columns