this post was submitted on 19 Jul 2024
1203 points (99.5% liked)
Technology
60052 readers
3169 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's not a flaw with Windows causing this.
The issue is with a widely used third party security software that installs as a kernel level driver. It had an auto update that causes bluescreening moments after booting into the OS.
This same software is available for Linux and Mac, and had similar issues with specific Linux distros a month ago. It just didn't get reported on because it didn't have as wide of an impact.
They skimp on QA?
Because most data center admins using linux are not so stupid to subscribe to remote updates from a third party. Linux issues happen when critical package vulnerabilities make it into the repo.
Tell me how you haven't worked as a sysadmin again.
This wasn't some switchable feature. The only way I've seen to stop this software from auto updating (per some comments on Hacker News/Y Combinator) as it chooses is by blocking the update servers at the firewall or through DNS black holing.
And yes, they chose to use this software. Look. Crowdstrike bought a fucking SuperBowl ad, a bunch of executives drank the kool aid, and a lot of tech departments were told that they'd be rolling this software out. That's just how corporate IT works sometimes.
I was saying:
Your response is not related in any way to that. If a third party software - running on system rights - forces auto-updates, that's called a "rootkit" and any sane admin would refuse to install such a package.
Competent here also meaning "if the upper management refuses to listen to my advice, I leave because I have other options". People who implement stupid policies - and especially technological solutions - against their principles are a cancer to democracy. Those are the people that enable tech-illiterate morons to implement totalitarian regimes.
Still a MS issue. Both testing and rollout procedures were inadequate
But MS had nothing to do with both the testing and rollout?
It's a broken 3rd party component. Croudstrikes testing and rollout procedures were inadequate.
How is it Microsoft's fault when a third party software bricked the OS?
My Windows gaming PC is completely fine right now, because I don't use crowd strike. Microsoft didn't have anything to do with crowd strikes' rollout or support.
I love Linux and use it as my daily driver for everything besides some online games. There are plenty of legitimate reasons to criticize Microsoft and Windows, but crowd strike breaking stuff isn't one of them, at least in my opinion.
My bad i thought this went out with a MS update