mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #506] --ignore=net does not work. Should it? #356
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#356
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 @vn971 on GitHub (May 8, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/506
Currently,
--ignore=netdoes not ignore a--netcommand. Should it, by design?Steps to reproduce:
firejail --noprofile --ignore=net --net=none --ignore=net ping 8.8.8.8Expected: successful ping. Actually: "network unreachable".
@pyamsoft commented on GitHub (May 9, 2016):
Ignore only ignores options specified in profile files, not on the command line.
Because net is entered on the command line, it will not be ignored.
@netblue30 commented on GitHub (May 10, 2016):
Yes, it only ignores commands in profile files.
@vn971 commented on GitHub (May 10, 2016):
@pyamsoft @netblue30 oh, you're right.
I don't know how I would prefer things to be (ignore CLI arguments or not), but at least the current behavior is documented, and makes sense. (People rarely concatenate arguments in my experience, although I did.)
Closing for now.
Thanks.