CrowdStrike broke Debian and Rocky Linux months ago, but no one noticed

13 Comments

  1. Woodden-Floor

    It would be better if technicians implemented the qubes network server and installed windows inside QubesOS.

  2. Minechris_LP

    They could have taken one hour and rolled it out to 10000 computers and check, if anyone was complaining. Deployment in multiple waves is nothing new.

  3. TONKAHANAH

    Yeah, i’ve been reading a bit about this. Red Hat posted bug reports to them about it breaking a similar file in a similar way months ago.

    only real difference is there are almost no user end systems running red hat or debian by comparison.

  4. Cool_As_Your_Dad

    Linux fanboys not going to like this… ( that its was not only windows having the issue)

    ​

    “rowdstrike support acknowledged the issue, highlighting a pattern of inadequate testing ‘

    Yes.. fire all those QA people etc… save a few bucks.

    Edit. Its 2 replies not linked to each other

  5. Gorexxar

    Do they even test deploying to Operating Systems or do they just deploy blind?

  6. abbbbbcccccddddd

    Ridiculous that they didn’t learn anything from it, and neither did their customers.

  7. cueball86

    I hope Crowdstrike becomes a verb in the vocabulary of every tech worker when describing massive fuck up. Should make it as an entry in Urban dictionary

  8. The_All_Seeing_Pi

    No, an update caused a problem but was caught before release. What is this bullshit?

  9. Metaltikihead

    People running linux machines don’t use crowdstrike. Crowdstrike is basically used on end user business machines.

  10. Okay so all that says is they knew they were bricking systems and still went with it.

  11. Burgergold

    Trellix broke 2 rhel here by putting a pam lib in quarantine

    Wasnt able to ssh with password or log on console with root/password

    I was lucky to be able to use a ssh key

  12. numb3rb0y

    I wish these discussions weren’t so reactionary. Yes, Microsoft did not cause this. And I think most people here don’t actually want super locked down walled gardens on their PCs, so bad drivers are probably always going to be a potential problem.

    But OTOH Linux is free, no-one is actually obligated to make it secure. Microsoft doesn’t have that excuse. I’m not demanding perfection, I know no program with so many lines of code is going to be perfect, but it still feels like a joke that the default assumption is that we should rely on third party cybersecurity solutions when Microsoft is actually charging for a commersial OS. And they absolutely do have a well documented history of prioritising end-user ease-of-use over good security practises, just look at how horribly privileges were handled before Vista, for Christ’s sake. We *still* have developers trying to use Program Files to store transitory data because that was just how it was done for decades.

Write A Comment