2 ms·
It's simple: the failure is not specific to the OS. Crowdstrike runs on MacOS and Linux workstations too. And it's just as dangerous there; the big thread has
by TeMPOraL 2y ago
It's simple: the failure is not specific to the OS.
Crowdstrike runs on MacOS and Linux workstations too. And it's just as dangerous there; the big thread has stories of Crowdstrike breaking Linux systems in the past months.
Crowdstrike isn't needed by/for Windows, it's mandated by corporate and government bureaucracies, where it serves as a tool of employee control and a compliance checkbox to check.
That's why it makes no sense to blame Microsoft. If the world run on Linux, ceteris paribus, Crowdstrike would be on those machines too, and would fuck them up just as bad globally.
- BHSPitMonkey 2y ago> That's why it makes no sense to blame Microsoft. If the world run on Linux, ceteris paribus, Crowdstrike would be on those machines too, and would fuck them up just as bad globally. CrowdStrike _is_ running on a massive number of Linux servers/endpoints, with the same kind of auto-update policies.
- machine_coffee 2y ago>Crowdstrike runs on MacOS and Linux workstations too. This is what chills me to the bone, there's loads of these installations worldwide on heterogeneous OSs but with very little oversight of the code. Companies have basically rolled over and stated, 'OK, we trust you' I'm not usually a fan of strident calls to open source everything, but the source code at least for the channel file parser on all OSs should now be made public so that we can have an oversight of what so many have placed their trust in.