They mean after Crowdstrike gets sold, the new company promises a more rigorous QA, and quietly rebrands it.

I read on another thread that an admin was emulating a testing environment by blocking CrowdStrike IPs on their firewall for the whole network before each update, with the exception of a couple machines. It's stupid that he has to do this but hey, his network was unaffected

Serious question, can you not? There isn't an option to...like...set a review system first?

We would if we were able to control their “deployable content”.

Minimum safe distance.

not sure if you're being sarcastic, but if anything this news paints linux deployment in an even better light.

Are you shocked that bad software can crash multiple operating systems or something?

A lot of companies use debian

We use Alma, which is basically Rocky. Before that, CentOS. Lots of people don't need or want the expensive support contracts.

OSS support though donations and commits is the way to go unless you get value out of those contracts (we would not).

I don’t know about that. In the HPC space we use a lot of EL distros. Mainly Centos & now Rocky. Most of the nodes run the os in ram too. Though almost all those kind of systems have no internet connection and don’t use things like crowdstrike. I’ve worked for a few places where the only part of the company that used windows was the office staff eg accounting, hr, etc. everything else is/was using an EL distro or upstream of one eg Fedora. Those type of places usually don’t mess things like crowdstrike for a lot of different reasons eg the kind of data they’re processing and security requirements on that data.

None of these things are used in actual server operations.

And it's not much more difficult to fix on Windows, except for the scale of the problem.

Good luck doing that remotely. Which is the sole problem with this most recent CrowdStrike bug.

And on Windows you booted in safe mode and removed one file. What's the point of your post?