mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #623] protocol unix makes netfilter useless... right? #435
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#435
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 @Fred-Barclay on GitHub (Jul 9, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/623
Just making sure... if I use
--protocol=unixthen all network (eth, wlan) access is disabled and there is no point in using a network filter such as netfilter or--net=none, right?--protocol=unixis turning out to be very useful when I want to disable network access but still need a dbus connection (which net none seems to block), so I want to make sure I'm using it correctly.Thanks!
Fred
@netblue30 commented on GitHub (Jul 9, 2016):
Yes, you are right. Some programs such as evince are just crashing with "--net=none", so I put --protocol=unix instead. It is almost the same thing. The difference is in one case you see the network but you cannot connect to it, and in the other case you don't see the network at all.
@Fred-Barclay commented on GitHub (Jul 9, 2016):
Thanks mate. :)