To avoid such issues in the future, CrowdStrike should prioritize rigorous testing across all supported configurations.
Bold of them to assume there's a future after a gazillion off incoming lawsuits.
this post was submitted on 22 Jul 2024
586 points (97.7% liked)
Technology
58073 readers
4583 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
I was listening to a podcast earlier, and they mentioned the fact that their legal liability may, in fact, be limited because of specific wording in most of their contracts.
In other words, they may actually get away with this in the short term. In the long-term, however, a lot of organizations and governments that were hit by this will be reevaluating their reliance on such monolithic tech solutions as crowdstrike, and even Microsoft.
So you may be right, but not for the reasons you think.
and even Microsoft
(x) doubt
They had decades to consider Microsoft a liability. Why start doing something about it now?
Literally lol'd. Thanks for that!
Contracts aren’t set in stone. Not only are those contracts modified before they are accepted by both parties, it’s difficult to limit liability when negligence is involved. CS is at worst going to be defending against those, at best defending against people dumping them ahead of schedule against their contracted term length.
load more comments
(3 replies)
They mean after Crowdstrike gets sold, the new company promises a more rigorous QA, and quietly rebrands it.
Slorp is now Bonto!
I think you mean after they sell their assets to a new company. Leave the lawsuits with the old company who will shut down.
Cloudstrike, wait no!
What are you doing Counterstrike
Additionally, organizations should approach CrowdStrike updates with caution
We would if we were able to control their "deployable content".
I read on another thread that an admin was emulating a testing environment by blocking CrowdStrike IPs on their firewall for the whole network before each update, with the exception of a couple machines. It's stupid that he has to do this but hey, his network was unaffected
Serious question, can you not? There isn't an option to...like...set a review system first?
For antivirus definitions? No, and you wouldn’t want to.
But it sounds like this added files / drivers or something, not just antivirus rules?
Turns out it was a content update that caused the driver to crash but the update itself wasn't a driver (as per their latest update.)
Found this post that explains what happened in detail: https://lemmy.ohaa.xyz/post/3522666
As an application developer (rather than someone who can/does code operating systems) I was just left open-mouthed …
Looks like they’re delivering “code as content” to get around the rigour of getting an updated driver authorised by MS. I realise they can’t wait too long for driver approval for antivirus releases but surely - surely - you have an ironclad QA process if you’re playing with fire like this.
Oh, wow.
load more comments
(4 replies)
But I've read so many posts on here about how Linux is flawless!
not sure if you're being sarcastic, but if anything this news paints linux deployment in an even better light.
This is good for Bitcoin
Are you shocked that bad software can crash multiple operating systems or something?
Nah, but there were some Linux evangelists claiming this couldn't possibly happen to Linux and it only happened to Windows because Windows is bad. And it was your own fault for getting this BSOD if you're still running Windows.
And sure, Windows bad and all, but this one wasn't really Microsofts fault.
The sane ones of us know well that a faulty driver is a faulty driver, but! Linux culture is different. Which is why this happened so spectacularly with Windows. EDIT: and not with Linux
load more comments
(2 replies)
load more comments
(6 replies)
I'm not shocked at all, but there seems to be a very sizable number of people on Lemmy who think if people just used Linux there'd never be another problem or exploit again, which is ridiculous. Mac users used to feel the same way until the market share started to grow and all of the sudden you're seeing news of serious exploits.
load more comments
(8 replies)
Companies don't really use Debian or Rocky in widescale production because they have no support.
Now red hat or ubuntu is a different matter.
Honestly though this does point out that this is a pattern of behavior on crowdstrikes part. This should have been the canary in the coalmine.
We actually use rocky and I think Debian at work for servers. We are currently migrating away from EOL centos .
A lot of companies use debian
We use Alma, which is basically Rocky. Before that, CentOS. Lots of people don't need or want the expensive support contracts.
OSS support though donations and commits is the way to go unless you get value out of those contracts (we would not).
I don’t know about that. In the HPC space we use a lot of EL distros. Mainly Centos & now Rocky. Most of the nodes run the os in ram too. Though almost all those kind of systems have no internet connection and don’t use things like crowdstrike. I’ve worked for a few places where the only part of the company that used windows was the office staff eg accounting, hr, etc. everything else is/was using an EL distro or upstream of one eg Fedora. Those type of places usually don’t mess things like crowdstrike for a lot of different reasons eg the kind of data they’re processing and security requirements on that data.
In April, a CrowdStrike update caused all Debian Linux servers in a civic tech lab to crash simultaneously and refuse to boot.
And then, you boot their servers from a Linux Live USB, run TimeShift to restore the last system snapshot, refuse the latest patch from Cloudstrike and they all lived happily ever after.
None of these things are used in actual server operations.
And it's not much more difficult to fix on Windows, except for the scale of the problem.
Good luck doing that remotely. Which is the sole problem with this most recent CrowdStrike bug.
load more comments
(1 replies)
And on Windows you booted in safe mode and removed one file. What's the point of your post?
load more comments
(1 replies)
Because Linux sysadmins know to test a fucking update before applying to the whole company
load more comments
(1 replies)
Microsoft already has a very bad reputation, so they will be blamed for every issue on their OS.
Vista suffered from bad 3rd party drivers, then people proceeded to just dunk on M$ due to their already bad name. Despite Edge is nowadays just a different flavor of Chromium, people are still making "haha IE slow" memes, even those that still claim Google being the "savior of the internet".
So in the end, they is an internal contradiction in capitalism. It just append to be collapse due to lack of ressources and dumb management
load more comments
(7 replies)
view more: next ›