Indeed, the major problems with macOS 15, which has been available for a week, should have been resolved, after all, a beta phase has been running since the beginning of June; however, major security companies have now reported problems with their filtering and protection programs, which means that users should not use them with the new Mac operating system Sequoia: apparently their entire functionality is partially disrupted.
Advertisement
Developers are angry in anticipation of macOS 15.1
Difficulties have been reported by companies such as CrowdStrike, Microsoft, SentinelOne. ESET And well-known security expert Patrick Wardle reports about smaller companies like DoubleU. Objective Development from Vienna, the creator of the network filter Little Snitch, also advises not to use macOS 15 initially. MacOS 15 still has “many errors in the areas of network and firewall” that can cause “data corruption” in TCP connections. Christian Starkjohn from Objective Development told Mac and I that it is possible to use Little Snitch 6 on Sequoia, but the software only works “as the system allows.” Now we are hoping for macOS 15.1 and quick bug fixes.
Wardle said told TechCrunchIt’s “incredibly frustrating that you always have to deal with the fact that users are angry and blame their own tools for breaking the Mac.” But it’s definitely Apple’s fault “It’s hard to write error-free software.” But Apple should probably spend less money on marketing and more money on software testing. “Then we’d all be better off!” Why the security companies apparently only noticed the problems with the general release of macOS 15 or whether there were bugs in them that were already reported without Apple fixing them at the beginning remains unclear.

TCP packets garbled, DNS requests thrown away
So far it is only partially clear what exactly is happening with macOS 15. On Reddit and other forums, the problems are mainly divided into two areas. For some connection types, active network filters (via Apple’s Network Extensions Framework, which security tools use) cause connection problems at the TCP level – presumably because they crash. For example, this applies to ssh
via the terminal, but also for other routines. ssh
For example, error messages such as “connection corrupted” or “wrong key size” pop up. Connections work without network filters. However, sometimes unexpected connection problems occur while surfing the web, even when reloading content.
If Apple’s own app firewall was also active, all incoming UDP packets were suddenly blocked – at least in some applications. This also affects DNS requests in browsers such as Firefox (apparently not Chrome and Safari), which then do not work. According to Starkjohn, this has to do with the different developer interfaces through which UDP packets can be accessed. Objective Development recommends simply turning off the Apple firewall until a solution is available – this is also an unpleasant solution. Still seems to be the case Shared networking for virtual machines no longer works or just stutters and DHCP no longer allocates IPs to Macs. VPN clients like NordVPN are also apparently affected.
(B.Sc.)
