←back to thread

158 points kenjackson | 1 comments | | HN request time: 0.619s | source
Show context
rramadass ◴[] No.41031248[source]
I had read reports of this earlier which is what makes me speculate that the Windows Crowdstrike issue is more than "just a update error" i.e. there might be some nefarious hand behind this. Given that they were already aware of the Linux issue it boggles my mind that they did not take extra precautions when it came to Windows updates. We will have to wait and see for further trustworthy info.

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

replies(3): >>41031293 #>>41031643 #>>41032173 #
bawolff ◴[] No.41031293[source]
Some part of a company already aware of an issue but different part still ships is a pretty common tale and seems much more likely than some nefarious conspiracy theory. (And that is even assuming this is the same issue, which seems questionable)

After all, who exactly would benefit from such a nefarious scheme to crash windows computers? Certainly not Crowdstrike.

replies(3): >>41031325 #>>41031441 #>>41031502 #
1. tgv ◴[] No.41031325[source]
Wrt trying to get something out of the crash: https://www.theregister.com/2024/07/19/cyber_criminals_quick.... The conspiracy-minded could be suspicious of the quick response to this outage. "They must have known in advance!" Or they could suspect an overeager account manager at Crowdstrike, who wanted to show how important the product is.

But indeed, this really sounds like it was an internal error.