Btw - The article mentions Dave Plummer's analysis of the issue which might be easier for people to understand and worth a watch. - https://www.youtube.com/watch?v=wAzEJxOo1ts
Btw - The article mentions Dave Plummer's analysis of the issue which might be easier for people to understand and worth a watch. - https://www.youtube.com/watch?v=wAzEJxOo1ts
Like, this is not new. They, as an industry, have been a byword for shoddy nonsense for literally decades.
And as security tools break a lot of security norms - like sandboxing, least privilege, and running in userspace - you might think such enthusiasts would make sure they were coded with the utmost care. That this team of secure coding all-stars would be code reviewing, managing scope, fuzz testing, static analysing, formally validating and suchlike, as befits code running with the highest privilege levels.
Surely huge multinational corporations wouldn't grant unlimited privileges to kernel modules written by clowns.... would they?
If you believe the crowdstrike marketing, I can see how you might think shadowy saboteurs are the only plausible explanation.
Eh, I mean, you might think that, absent any other information about the industry, but they're largely not.