How did the update get through testing, if the bug has an immediately obvious catastrophic effect?
this post was submitted on 19 Jul 2024
169 points (96.7% liked)
Technology
59063 readers
3470 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
Agreed, this seems like a pretty obvious failed smoke test.
Three options seem likely to me: the build was untested, the final package got corrupted after testing, the test environment has some kind of abberant config that hid the defect.
Kernel drivers are "reviewed" and signed by Microsoft for exactly this reason. It's a security risk if any program an administrator runs could load malicious kernel drivers into windows
Something I have heard (take with a grain of salt) is that there was a new windows update that went out just before the crowdstrike update. And the issue happened with the new windows update.
Not the case. I have dozens of servers last updated in May that crashed.
Pretty good test to see how easy it would be to shut the world down. Uninstall CrowdStrike.
I'm sure Russia is taking note. Its computers were unaffected due to having no Crowdstrike installations. China too, apparently.
I’m sure they have their own solution for that, but yes, it would be unwise for a government to install software maintained by a foreign country. Kind of like voting booths.
China and Russia are switching to Linux, too.
Read-only friday, right? Right...?
Poor sysadmins.
And this happens the same week that Kaspersky left the U.S.
They are laughing internally right now.
Kaspersky has caused BSODs because of updates in the past as well. Hardly an AV maker hasn't. The problem here is that Crowd Strike has captured the enterprise market in a large portion of the globe.
Oh I'm well aware. I hated deploying Kaspersky. But we switched to Crowdstrike last year and now this happened. Just a funny coincidence.
Luckily, we're a small company and a third use Macs. The others, well, I had three PC laptop and one virtual server issues. Not too bad. We're on the West Coast so glad I was aware of it last night when Australia got issues.
Every time our IT tells PC users to just leave their computer on for X hours so it gets updates, I wonder how that can be a great system.