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.’”

    • floofloof@lemmy.ca
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      I’m sure Russia is taking note. Its computers were unaffected due to having no Crowdstrike installations.

      • radivojevic@discuss.online
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        I’m sure they have their own solution for that, but yes, it would be unwise for a government to install software maintained by a foreign country. Kind of like voting booths.

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

      Two quick points, given the massive impact of this even it is clear to say many critical systems run windows. Meaning them being windows doesn’t make them “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
        0
        ·
        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.

      • Kairos@lemmy.today
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        4 months ago

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

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

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

        • Guest_User@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          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

  • floofloof@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    How did the update get through testing, if the bug has an immediately obvious catastrophic effect?

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

      Something I have heard (take with a grain of salt) is that there was a new windows update that went out just before the crowdstrike update. And the issue happened with the new windows update.

    • Telorand@reddthat.com
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      Agreed, this seems like a pretty obvious failed smoke test.

      Three options seem likely to me: the build was untested, the final package got corrupted after testing, the test environment has some kind of abberant config that hid the defect.

      • Justin@lemmy.jlh.nameOP
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        Kernel drivers are “reviewed” and signed by Microsoft for exactly this reason. It’s a security risk if any program an administrator runs could load malicious kernel drivers into windows