this post was submitted on 19 Jul 2024
358 points (97.1% liked)
Microblog Memes
5388 readers
2771 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
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
The real blame lies on the fact that Windows lets hundreds of companies like Crowdstrike ship kernel-level software to millions of computers. The fact that this incident was caused by an accidental bug is hilarious, but we're lucky that it wasn't someone pushing malicious software instead.
Windows drivers are a huge liability and I wouldn't be surprised if the next time is a state actor like Russia pushing kernel-level malware.
I hate how many video games come with kernel level anti cheat, it’s an attractive target for hacks
The helldivers community fucking hates me for pointing this out. Don’t buy helldivers, or any other game packaged with such bullshit.
Is helldivers anticheat kernel level? I play it just fine on Linux.
Yup. NProtect Gameguard. They got called out for it on day one, but then everyone was like “wow this game is good, so never mind!” Arrowhead CEO outright admitted to it but claimed it’s normal and necessary.
To me it’s like if some company wanted to dig through my mail whenever they wanted and defended themselves with “but we won’t do anything malicious! Its to keep you safe!” They can fuck right off with that nonsense.
but but, it's in character for the canon!!
The real fuck up is that Crowdstrike Falcon can auto update through its own updater, and doesn't have any kind of control panel for management that could be used for change control. If their customers could have tested this update first, none of this would be happening.
Or if they were smart enough to do a phased rollout to a small percentage of users before deploying worldwide. That catches most issues quickly.
Or if Microsoft reviewed drivers before signing them.
I think they do (or at least I've seen it mentioned), but this wa apparently caused a by a bad configuration fil for that driver. (A 40-something kB file pf pure zeroes)
or like, tested the fucking update at all...
Yep. A lot of customers were running n-1 or even n-2 of their falcon sensor release to mitigate risk. Doesn't count for shit though if the "deployed content" bypasses all of that.
an antivirus-like software is something you want auto updates for in my opinion
Let's be real, Microsoft wouldn't do a hell of a lot better even if they had that stuff locked down. Their fuckups just tend to hit the general public a little more frequently than enterprise customers.
Edit: I wrote this before I learned about yesterday's Azure outage lol. That definitely adds to my point.
Yeah this way they can Shaggy their way out of it
so you're saying you shouldn't be able to install any software with drivers? there's nothing microsoft can do about mass installing a program with elevated privileges, especially if it had actual uses like this
The average person or IT dept should not have to, no. It is very rare to install third party drivers on MacOS and Linux, and the fact that it's even needed for an antivirus is insane.