Get the latest tech news

What everyone seems to be missing in the CrowdStrike incident


Introduction 25 years ago, I said (really, I did!) that automatic software updates pose a greater risk than malware (ok, at that time we really only had viruses). Many incidents since than has proven this right, but none more so than the CrowdStrike Falcon Blue Screen of Death (BSOD) incident on July 19, 2024.

Doing the extraction, or discovery if you like, of translatable strings from a structured source like a .resx file is easy, solid and dependable - and fits the general development model of .NET better than wrapping all texts in T() method calls, similar to the original C-style gettext mode of operations. But, unfortunately it turns out this is a little too slow, and also we're overloading the back end search service which has a rate limiting function as well as a per-call pricing schedule so it's expensive too. The scary thing is, everything will still work, and look nice during testing but if these objects are placed in a HashTable or Dictionary or similar, and in production they grow to a larger number of elements then indexing these collections degenerate into linear searches in a linked list.

Get the Android app

Or read this on Hacker News

Read more on:

Photo of CrowdStrike

CrowdStrike

Photo of CrowdStrike incident

CrowdStrike incident

Related news:

News photo

CrowdStrike boss Kurtz called to testify before Congress

News photo

The CrowdStrike fail and next global IT meltdown already in the making

News photo

How did a CrowdStrike file crash millions of Windows computers? We take a closer look at the code