[bryanrasmussen]

wait, did the open source community have access to Microsoft's code and then fail to find the Cloudstrike vulnerability even though they had the same amount of time with that code that MS had with theirs?

I mean open source idea is that even MS engineer can find their problems.

And then MS engineer found their problems.

So yeah, does seem like a win for open source ideas which is not even something I particular care about...

[Tabular-Iceberg]

Do you really need to read MS source code to figure out that it has a kernel module loading mechanism?

[gjsman-1000]

> wait, did the open source community have access to Microsoft's code and then fail to find the Cloudstrike vulnerability even though they had the same amount of time with that code that MS had with theirs?

Cloudstrike was not in Microsoft's code; so yell at Cloudstrike.

> And then MS engineer found their problems.

The Microsoft engineer found the malicious code from the binary first - the same way he would have investigated proprietary software. The fact that it was open source didn't help discover the vulnerability in any way. The open source nature only helped with explaining how it got in there afterwards.

> So yeah, does seem like a win for open source ideas which is not even something I particular care about...

According to many security researchers, the `xz-utils` thing was deeply underrated and shows how, let's just say, not necessarily more secure open source software is. The fact that every Linux computer was nearly backdoored, globally, and it was found by accident, by a Microsoft engineer nonetheless, without any use of the code to find the bug, after that code was approved by both Debian and Red Hat, looks terrible to the open source community.

I take that back. It doesn't just look bad - it is bad. The ideology and security assumptions are in question, bad. If Microsoft's engineer had not found that bug, Linux and open-source as a whole could have sustained a mortal wound and a crushing blow to the theory of open-source being more secure.

[CRConrad]

> Cloudstrike was not in Microsoft's code;

Yes of course it was; it ran in kernel space. Microsoft let it in, ao it was in there.

> so yell at Cloudstrike

Sure. And Microsoft.