Linux

5376 readers

15 users here now

A community for everything relating to the linux operating system

Also check out !linux_memes@programming.dev

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 1 year ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

468

CrowdStrike broke Debian and Rocky Linux months ago, but no one noticed (www.neowin.net)

submitted 4 months ago by lemmee_in@lemm.ee to c/linux@programming.dev

62 comments fedilink hide all child comments

A widespread Blue Screen of Death (BSOD) issue on Windows PCs disrupted operations across various sectors, notably impacting airlines, banks, and healthcare providers. The issue was caused by a problematic channel file delivered via an update from the popular cybersecurity service provider, CrowdStrike. CrowdStrike confirmed that this crash did not impact Mac or Linux PCs.

It turns out that similar problems have been occurring for months without much awareness, despite the fact that many may view this as an isolated incident. Users of Debian and Rocky Linux also experienced significant disruptions as a result of CrowdStrike updates, raising serious concerns about the company's software update and testing procedures. These occurrences highlight potential risks for customers who rely on their products daily.

you are viewing a single comment's thread
view the rest of the comments

[–] SkyNTP@lemmy.ml 89 points 4 months ago (5 children)

The software is not the problem. Software breaks all the time. The problem is monocultures and centralization. Building entire industry ecosystems all around a single point of failure. This is the just-in-time manufacturing supply chain disruptions and fragility all over again.

Who knew, a diverse ecosystem was a strength, not a weakness.

[–] Ooops 45 points 4 months ago (1 children)

The software is the problem if it's produced with a corporate mentality of "ship first, fix later".

[–] SapphironZA@sh.itjust.works 11 points 4 months ago

Yep, at this point the "security" companies can do with imitating malware development practices.

load more comments (3 replies)