169
How One Bad CrowdStrike Update Crashed the World’s Computers
(www.wired.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Jul 2024
169 points (96.7% liked)
Technology
59419 readers
2926 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
Two quick points, given the massive impact of this eveny it is clear to say many critical systems run windows. Meaning them being windows doesn't make them any less "actual computers".
Also, the OS in this event is irrelevant. They could have botched an update to their Linux version and crashes all the Linux boxes leaving windows untouched. This was not a result of an issue of any OS but a bad update.
They are less of an actual computers in a sense that they are not running stuff under their owner / operator control. This would happen in Linux with much lower chances, because there are no side update channels to such a critical component of the system used there.
However, to take back what I just wrote :) - I am sure rightly motivated engineers would be able to build such a security hole into Linux too, under enough pressure from bad corporate decisions.
What do you mean “no side update channels”? There are lots of software that update outside of a distro repo and lots of software that pulls metadata from the internet that could cause an error in the parser.
Linux stuff generally doesn't crash if a file gets deleted. It'll just fail to boot.
Neither does window. A file deletion did not cause this. A human at Crowdstrike uploaded a bug to production. Bugs in production can happen on any OS, this is just a terrible, terrible look for Crowdstrike because they seriously messed up
I mean, the end result would be the same: Large tracts of infrastructure not loading and causing hell
Have you read anything about this? A file deletion is the workaround for affected hosts, silly!
?
I was just trying to point out that you implied a file deletion is what's causing this, and Linux wouldn't crash. This fault is fixed by deleting a file, ironically