Re:Apple's new macOS Sequoia update is breaking some cyberse...
by inkyoto on Friday September 20, 2024 @10:14PM
(#41606944)
It apepars that the default application firewall blocking rules are overly restrictive.
There are two «firewalls» in OS X: the IP packet filter (controlled pfctl) and the application level one (controlled by /usr/libexec/ApplicationFirewall/socketfilterfw). The one that is causing a lot of grief for upgraded users is the latter one.
The workaround is to remove/disable the app level blocking rules manually:
There are two «firewalls» in OS X: the IP packet filter (controlled pfctl) and the application level one (controlled by /usr/libexec/ApplicationFirewall/socketfilterfw). The one that is causing a lot of grief for upgraded users is the latter one.
The workaround is to remove/disable the app level blocking rules manually:
1. Get a list of app level firewall rules:
2. Locate the app(s) of interest.3. Disable the app specific rules:
Alternatively, the app can be removed from the list of application firewall rules: That will fix the problem, e.g. with Firefox (tested) or WireGuard (reported by somebody else above, untested).If a DoH DNS configuration is used, it also makes sense to explicitly whitelist the DoH provider in «pfctl» rules at IPv4/IPv6 and domain levels.