I remember using this sort of applications on Windows (a very long time ago; those were the days of Windows 98, whose famous stability drove me to Linux and BSD). Can some of its users help me shed some light on the use case of such a program on an open source system? I mean: - Signed packages from trusted repos should not need firewalling, at least not if you're using a serious distro rather than a hobby project. Th…
Douane personal firewall for GNU/Linux
21–30 of 46 posts
Re: Douane personal firewall for GNU/Linux
#22I remember using this sort of applications on Windows (a very long time ago; those were the days of Windows 98, whose famous stability drove me to Linux and BSD). Can some of its users help me shed some light on the use case of such a program on an open source system? I mean: - Signed packages from trusted repos should not need firewalling, at least not if you're using a serious distro rather than a hobby project. Th…
Re: Douane personal firewall for GNU/Linux
#23Re: Douane personal firewall for GNU/Linux
#24I like the Little Snitch style "allow/deny per binary" thing. It's really unfortunate that it needs a new kernel module because current default firewalls (pf, iptables, etc.) only operate on IP addresses don't know anything about processes.
The traditional way to filter a program's network traffic with netfilter is to give each software its own uid, which can then be filtered. You will need it anyway to set ulimits and file access rights.
Also avoid to decide policy by process name. Even using full path is problematic (where things like hard links can give nasty surprises). Better to do what SELinux does and tag executables with metadata instead. Any role based system will be much more expressive, but also complex, than a uid based one.
Re: Douane personal firewall for GNU/Linux
#25I remember using this sort of applications on Windows (a very long time ago; those were the days of Windows 98, whose famous stability drove me to Linux and BSD). Can some of its users help me shed some light on the use case of such a program on an open source system? I mean: - Signed packages from trusted repos should not need firewalling, at least not if you're using a serious distro rather than a hobby project. Th…
Signed packages from trusted repos should not need firewalling, at least not if you're using a serious distro rather than a hobby project. Software has security vulnerabilities. So, even if the software is trusted, there could be a zero-day vulnerability that is exploited. I'd rather have software stopped in its tracks. (For this reason I think something like Little Snitch or Douane is not enough, you also need sandb…
How? When the zero day hits, the program has long been marked as trusted and the firewall will just happily let it go along. Besides, even if you're an experienced user and the firewall is smart enough to figure out that the application is talking to a server that it's never talked before (which isn't even sustainable for a lot of applications), it's very likely that you'll see the alert way before you read the news about the zero-day, and you'll just shrug and allow it to continue because you trust that program.
(Edit: maybe personal firewalls got smarter since I last used one and there's something else I'm missing here?)
> Maybe macOS apps are different, but I never had this experience during while using little snitch for almost 10 years.
The kind of applications that actively snoop on users as a business model -- the ones that you want to block in the first place -- sometimes even do this deliberately (which is something that I know from experience, not something that I suspect). Inexperienced users quickly figure out it's the firewall that gives them trouble, and they'll pick disabling the firewall over not playing with their toy any time. This works for pretty much any sort of permissions.
For example, last time I ran it on my tablet, Instagram's application was crippled to uselessness because I had disabled camera access (my girlfriend only needed to post a photo on an account that she managed): as soon as it opened, it spit out a big fat error message saying it can't access the camera and that you should allow camera access if you want to be able to take photos. As soon as you tapped ok, the same error popped up, and the application never loaded.
macOS apps aren't any different, you're just running the right ones :-).
Re: Douane personal firewall for GNU/Linux
#26I remember using this sort of applications on Windows (a very long time ago; those were the days of Windows 98, whose famous stability drove me to Linux and BSD). Can some of its users help me shed some light on the use case of such a program on an open source system? I mean: - Signed packages from trusted repos should not need firewalling, at least not if you're using a serious distro rather than a hobby project. Th…
There is a murky gray zone between actively malicious and fully privacy respecting applications. Applications in this zone are more prevalent in closed source software, and Linux is increasingly being used to run such software.
Re: Douane personal firewall for GNU/Linux
#27I like this. Linux has been missing a personal firewall with good GUI for a looong time. I'll probs give it a try on a VM and see how well it works.
Re: Douane personal firewall for GNU/Linux
#28"Latest commit by zedtux over 2 years ago" well. but TBH, I'd love to see some Little Snitch-like thingy on Linux.
https://github.com/subgraph/fw-daemon
it provides a very close experience to little snitch
Re: Douane personal firewall for GNU/Linux
#29Nice project and makes you think why all programs are given all network access by default. This page lists nothing under Packages but the author has actually made AUR packages for Archlinux: https://github.com/Douane/Douane/wiki/Archlinux-Packaging Here's a directly link to the installation instructions for anyone who'd want to try it out https://github.com/Douane/Douane/wiki/Compilation
One trick I learned to negate that is to insert an iptables rule that blocks all out-of-LAN traffic except for specific secondary user-groups. Not primary groups, but ones which you have to manually grant to users.
Then, those applications which you do wish to access the Internet can be run using sg e.g.
sg bobs_internet_access_group firefox
Anything that tries to run as a user's primary group is stopped at the firewall. For example a malicious shell script will run by default with the primary group and will fail.This is also very useful for stopping anything run by root from talking to the Internet, since that is a thing that should NEVER occur.
It does take a little configuration and it's probably best to create a new secondary group for each user ( and don't forget IPv6! ) but once it's set it just keeps working.
Re: Douane personal firewall for GNU/Linux
#30I like this. Linux has been missing a personal firewall with good GUI for a looong time. I'll probs give it a try on a VM and see how well it works.
Have you tried GUFW or Firewall Builder? Do you not consider them to have a good GUI? I remember about 10 years ago I used to use Firestarter (now defunct it seems), but that seemed acceptable.