They mean after Crowdstrike gets sold, the new company promises a more rigorous QA, and quietly rebrands it.
Comment on CrowdStrike broke Debian and Rocky Linux months ago, but no one noticed
viking@infosec.pub 3 months ago
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.
mipadaitu@lemmy.world 3 months ago
captain_aggravated@sh.itjust.works 3 months ago
Slorp is now Bonto!
bitchkat@lemmy.world 3 months ago
I think you mean after they sell their assets to a new company. Leave the lawsuits with the old company who will shut down.
Default_Defect@midwest.social 3 months ago
Cloudstrike, wait no!
derpgon@programming.dev 3 months ago
What are you doing Counterstrike
finley@lemm.ee 3 months ago
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 organizations as crowd strike, and Microsoft.
rumschlumpel@feddit.org 3 months ago
(x) doubt
They had decades to consider Microsoft a liability. Why start doing something about it now?
catloaf@lemm.ee 3 months ago
Because cybersecurity is becoming more of a priority. The US government has really put their attention on it in the last few years.
Tinidril@midwest.social 3 months ago
I was in IT back in 2001 when the Code Red virus hit. It was a very similar situation where entire enterprises in totally unrelated fields were brought down. So many infected machines were still trying to relocate that corporate networks and Internet backbone routers were getting absolutely crushed.
Prior to that, trying to get real funding for securing networks was almost impossible. Suddenly security was the hottest topic in IT and corporations were throwing money at all the snake oil Silicon Valley could produce.
That lasted for a couple years, then things started going back to business as usual. Microsoft in particular was making all sorts of promises and boasts about how they made security their top priority, but that never really happened. Security remained something slapped on at the end of product development and was never allowed to interfere with producing products demanded by marketing with inherently insecure designs.
Maeve@kbin.earth 3 months ago
Hard to tell, sometimes.
Maeve@kbin.earth 3 months ago
Literally lol'd. Thanks for that!
Brkdncr@lemmy.world 3 months ago
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.
TheBat@lemmy.world 3 months ago
Oh so you can fire QA department, get absolutely destructive update to millions of systems across the globe and this gross negligence doesn’t matter because of magic words in a contract? I don’t think so.
finley@lemm.ee 3 months ago
That’s not what I said said
TheBat@lemmy.world 3 months ago
Then how else is their legal liability is limited?
They killed off their QA department to chase profits which resulted in a broken product that crippled hundreds of organizations across the globe.
They don’t get to just shrug, say oopsie, and point at the contract.