gunnarstahl wrote:
the firewall is not there to protect admins but to protect a system running macos.
And to make sure that not outside access to a machine happens in case it is running software that happens to listen to a port.
The default behaviour of the application firewall is to allow all access to any running software.
And that can be anything from a software being installed to a website running a malicious script.
If you are hosting a website running a malicious script, then the firewall is the least of your problems.
In any case the firewall makes sure that only software, that is supposed to listen to the outside world can access said outside world.
That is the exact opposite of what a firewall does.
And the firewall in macos until sequoia was easily enough configurable so that the aforementioned 'average joe' knew how to use it.
And this ease of use is gone. Hence it needs to be fixed. And no, the answer is not to just disable it.
Before Sequoia, the application firewall was riddled with bugs. Sure, it was easy enough to configure. It just didn't actually apply any of those configuration changes. 😄
If you want to argue that the built-in firewall needs to be fixed, I'm not going to argue with that. My point is that a false sense of security is worse than no security. If someone wants to host some kind of service on a Mac, they need to be aware that anyone in the world can access that service (assuming they know how to establish a route through their access point, of course - but let's keep it simple - I'm trying to make a point). The problem with the built-in firewall is that it appears to give people this warm fuzzy that they are "protected" somehow, when it does absolutely nothing of the sort.
Don't be upset that I'm telling you to disable it. Be upset that you've been misinformed.