mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2061] [cosmetic] --netfilter6= and restricted-network yes #1391
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#1391
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 @yumkam on GitHub (Jul 24, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2061
Originally assigned to: @startx2017 on GitHub.
When
restricted-network yes(or similar compile-time option) is set,--netfilter=is rejected (Error: --netfilter is only allowed for root), but--netfilter6=is not. Fortunately, it is no-op in this case: only--net=noneis allowed, and--netfilter6=is ignored when no bridges are configured (still, it would be better to be consistent, one way or other).@startx2017 commented on GitHub (Jul 25, 2018):
Same problem for --netns and for all netfilter commands in profile files. I'm working on a fix. I intend to remomve --enable-network=restricted from configure.ac script, and clean up the code.
@startx2017 commented on GitHub (Jul 26, 2018):
the fix is in, thanks for the bug.
@yumkam commented on GitHub (Jul 26, 2018):
If someone still relied on this compile-time option, it will be very nasty surprise for them (as
--enable-network=restrictedis now seems exactly equivalent to--enable-network).