31–40 of 42 posts
Break them again and again until people realize how useless they are.
Earlier quoted context omitted.
Please look past the fact that CrowdStrike is today’s, or yesterday’s, cultural whipping boy. They make software, and its users would like it to work. It’s not a good thing.
And it's their responsibility to make sure it works by testing on pre-release OS builds and implementing fixes when necessary.
"Suck it up"?
Cry harder, dirtbags.
> “As a developer of macOS security tools, it’s incredibly frustrating to time and time again have to deal with (understandably) upset users (understandably) blaming your tools for breaking their Macs, when in reality it was Apple’s fault all along,” I would like to understand this better. Were there not any beta releases that these companies could have tested with in advance? Or were changes made between the beta an…
Per Patrick Wardle, this was well reported to Apple during beta. https://x.com/patrickwardle/status/1836862900654461270
The betas are there for you to test your code against future Mac releases. Apple can and probably will take away APIs that your business is built around. Especially when those APIs are actually decreasing security.
> At this point, it’s unclear exactly what is the issue So, is this a bug in Sequoia or a change that affects these low-level tools? If the latter, they may not like it, but that’s par for the game on MacOS. (Tried reading https://x.com/patrickwardle/status/1836862900654461270 , referenced by sephamorr , but that link isn’t working for me)
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:
/usr/libexec/ApplicationFirewall/socketfilterfw --listapps
3. Disable the app specific rules:
/usr/libexec/ApplicationFirewall/socketfilterfw --unblockapp
/usr/libexec/ApplicationFirewall/socketfilterfw --remove
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.
Earlier quoted context omitted.
This is the part I'm missing too. Major versions are the time to ship braking changes, did none of these companies bother to test their software that mucks deep in the plumbing of the OS?
They did, reported it, nothing changed. It's an OS bug, you can't make it look good by invoking some generic "time to break" principle
Earlier quoted context omitted.
They did, reported it, nothing changed. It's an OS bug, you can't make it look good by invoking some generic "time to break" principle
Or they fixed a bug/loophole that allowed this software to function?
Earlier quoted context omitted.
I usually wait for a .4 update before upgrading. One time around Catalina there was a bug that broke USB-C docks.. Oh cool none of my devices work. Interestingly in that thread, 'Intel' is not mentioned once.
This reminds me of a joke about "windows users waiting for the service pack while macos is always stable" that a friend always rubbed in my face whenever I had some issue with windows a decade ago. And that I just sent a message yesterday to my team to wait before installing sequoia... But now I'll use your target of .4.
Earlier quoted context omitted.
And it's their responsibility to make sure it works by testing on pre-release OS builds and implementing fixes when necessary.
And when they report bugs to the vendor, and Apple just black holes those bugs, as they do in probably 99.8%+ of bug reports? "Suck it up"?