https://web.archive.org/web/20240719155854/https://www.wired.com/story/crowdstrike-outage-update-windows/

“CrowdStrike is far from the only security firm to trigger Windows crashes with a driver update. Updates to Kaspersky and even Windows’ own built-in antivirus software Windows Defender have caused similar Blue Screen of Death crashes in years past.”

“‘People may now demand changes in this operating model,’ says Jake Williams, vice president of research and development at the cybersecurity consultancy Hunter Strategy. ‘For better or worse, CrowdStrike has just shown why pushing updates without IT intervention is unsustainable.’”

  • Guest_User@lemmy.world
    link
    fedilink
    English
    arrow-up
    20
    ·
    edit-2
    4 months ago

    Two quick points, given the massive impact of this eveny it is clear to say many critical systems run windows. Meaning them being windows doesn’t make them any less “actual computers”.

    Also, the OS in this event is irrelevant. They could have botched an update to their Linux version and crashes all the Linux boxes leaving windows untouched. This was not a result of an issue of any OS but a bad update.

    • daddy32@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      4
      ·
      edit-2
      4 months ago

      They are less of an actual computers in a sense that they are not running stuff under their owner / operator control. This would happen in Linux with much lower chances, because there are no side update channels to such a critical component of the system used there.

      However, to take back what I just wrote :) - I am sure rightly motivated engineers would be able to build such a security hole into Linux too, under enough pressure from bad corporate decisions.

      • bamboo@lemm.ee
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 months ago

        What do you mean “no side update channels”? There are lots of software that update outside of a distro repo and lots of software that pulls metadata from the internet that could cause an error in the parser.

    • Kairos
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      8
      ·
      edit-2
      4 months ago

      Linux stuff generally doesn’t crash if a file gets deleted. It’ll just fail to boot.

      • Guest_User@lemmy.world
        link
        fedilink
        English
        arrow-up
        10
        ·
        4 months ago

        Neither does window. A file deletion did not cause this. A human at Crowdstrike uploaded a bug to production. Bugs in production can happen on any OS, this is just a terrible, terrible look for Crowdstrike because they seriously messed up

      • Rolder@reddthat.com
        link
        fedilink
        English
        arrow-up
        7
        ·
        4 months ago

        I mean, the end result would be the same: Large tracts of infrastructure not loading and causing hell

          • flambonkscious@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            4
            ·
            4 months ago

            I was just trying to point out that you implied a file deletion is what’s causing this, and Linux wouldn’t crash. This fault is fixed by deleting a file, ironically