[GH-ISSUE #2061] [cosmetic] --netfilter6= and restricted-network yes #1391

Closed
opened 2026-05-05 08:02:28 -06:00 by gitea-mirror · 3 comments
Owner

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=none is allowed, and --netfilter6= is ignored when no bridges are configured (still, it would be better to be consistent, one way or other).

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=none` is allowed, and `--netfilter6=` is ignored when no bridges are configured (still, it would be better to be consistent, one way or other).
gitea-mirror 2026-05-05 08:02:28 -06:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@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.

<!-- gh-comment-id:407754538 --> @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.
Author
Owner

@startx2017 commented on GitHub (Jul 26, 2018):

the fix is in, thanks for the bug.

<!-- gh-comment-id:408107535 --> @startx2017 commented on GitHub (Jul 26, 2018): the fix is in, thanks for the bug.
Author
Owner

@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=restricted is now seems exactly equivalent to --enable-network).

<!-- gh-comment-id:408116535 --> @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=restricted` is now seems exactly equivalent to `--enable-network`).
Sign in to join this conversation.
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#1391
No description provided.