this post was submitted on 02 Aug 2024
245 points (98.0% liked)
memes
10217 readers
2059 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's both Microsoft's AND Crowd Strike's fault.
Wait until you learn about CrowdStrike breaking Linux systems as well.
Just kidding, no need to wait, here's one article about it: https://www.neowin.net/news/crowdstrike-broke-debian-and-rocky-linux-months-ago-but-no-one-noticed/
Different events. Crowdstrike is really good at what they do (breaking systems).
Not to be smart, but just in conclusion: it'd have been pretty special, if they had broken down Linux and Windows with the same patch.
Would they receive the literal same patch? I thought it'd be different teams or something
it's Crowdstrikes fault 100%. Just because it caused Windows to crash because Microsoft let Crowdstrike have system driver level access isn't really Microsoft's problem. You wouldn't blame Microsoft if your video driver causes a crash when your video game loads would you? In a big picture kind of way maybe its Microsoft's problem because they enabled the situation to happen but that's not really in scope of what has actually happened.
But Microsoft designed the system such that they needed a level of access that allowed them to crash it. Microsoft could make changes that allowed the software to do what it needed with protections against letting that software crash the system. Basically a wrapper. Or, it could track updates to software that has such special access, and roll back updates after crashing more than once or something. It chooses not to. So it shares the blame because of that decision.
Anything with enough access to block malicious programs has enough access to block any other program by mistake.
Security modules like this usually get very invasive with the OS, to be able to monitor everything and so that malicious programs don't have the ability to shut it off.
Microsoft actually tried to make these changes to prevent the need for kernal drivers. However security companies called foul and the EU told ms to not continue. There was worry that defender would end up with better access than 3rd party products.
They could block that level of access but security software should be able to smack down attacks. And if those attacks are happening to those levels of computing, we become 100% reliant on the os vendor. This isn't a Microsoft problem, it's a problem for all each OS
Crowdstrike isn't necessary for Windows to work. It is an addon that asks system level authority.
Windows not having the ability to give apps system level authority would be an even worse situation.