@newt I am not 100% on this but I think that Windows kernel enforces a subset of C++ features so like you don't get try/catch but don't quote me on it.
@sun if you don't do basic checks, it shouldn't pass though MISRA and similar safety standards which this kind of high impact code really should use imo
@sun At the same time with a DSL I don't think even a safer language would have protected you, like you'd still have got either a bullshit value returned or a runtime crash. Plus like… don't put a custom interpreter in the kernel.
@sun I mean integration tests, not unit tests, which aren't that useful to prove that your software works for system components. Like doesn't really matters if your function works for few examples if the default config of Windows just blows up on it.
@RustyCrab@Inginsub I apologize I meant that if you're using vanilla C/C++ you are vulnerable to coding mistakes which just take more testing to catch, and static analysis isn't as good as it could be with other languages.
you can always write more unit tests, you can always do more integration testing, you can do staged rollouts.
I was listening to another video and apparently Crowdstrike for some reason is very hostile to the idea of staged rollouts, they have been asked and they were very vocally resistant. why???
@Inginsub@sun seconded. You don't just crash every computer in the world except for your test setup. Even if that was the case, that's why you do slow rollouts to specific or low risk businesses first to see of anything goes wrong. This is deployment 101.
@sun >I don't see how you could prevent this using technical means don't use regex in kernel Also I'm not buying it, somehow it crashed virtually every windows machine but their test setup.
@phnt@Inginsub@RustyCrab yeah I saw a document that showed they caused outages on linux every month for the past five months (just not literally every linux machine)
@sun@Inginsub@RustyCrab >I was listening to another video and apparently Crowdstrike for some reason is very hostile to the idea of staged rollouts, they have been asked and they were very vocally resistant. They take pride in being one of the best EDR options and generally being very quick to respond to threats. And now it got to them.
The software itself has configurable policies for updates and when they should roll out to your machines, but Crowdstrike still has the ultimate option to completely bypass your own policies, which that update did. This has some usecases, but I would generally prefer an emergency mailing list that companies can subscribe to in case of some random 0day that is detected. Automatic updates on AD controllers is stupid.
They also have a history of breaking OS installs. Basically the same thing also happened this year to Debian and RHEL installs, but that mostly swept under the rug.
But as people have been pointing out, this is a company which in four months crashed four different operating systems, one of their selling points is doing more than Windows, they just didn't give a damn until it likely killed the company. It is after all a notoriously political company and was founded and is run by a Jew.