I think people are missing the point here. The biggest problem was not that the update was bricking the machines, that could’ve happened to Linux/macOS/BSD etc. The problem is that the solution to the problem is to MANUALLY access the machine, get into safe mode and type some commands. This is insane.
And you should be able to EASILY disable automatic updates for apps like that on Windows Server.
I dunno, I’d say them deploying an update that bricked machines at the scale they did shows they didn’t test it very well at smaller scales. They could have even still used their users as beta testers, just needed to do a subset of them first.
I think people are missing the point here. The biggest problem was not that the update was bricking the machines, that could’ve happened to Linux/macOS/BSD etc. The problem is that the solution to the problem is to MANUALLY access the machine, get into safe mode and type some commands. This is insane. And you should be able to EASILY disable automatic updates for apps like that on Windows Server.
I dunno, I’d say them deploying an update that bricked machines at the scale they did shows they didn’t test it very well at smaller scales. They could have even still used their users as beta testers, just needed to do a subset of them first.
Crowdstrike exists for Linux. Are their reports their update affected Linux servers? I have not read that anywhere.