• mobius_slip@beehaw.org
    link
    fedilink
    arrow-up
    4
    ·
    2 months ago

    Microsoft chose to work with these people and accepted their faulty input. How is it not Microsoft’s fault?

    • Yoruio@lemmy.ca
      link
      fedilink
      arrow-up
      7
      ·
      edit-2
      2 months ago

      If you had a Samsung fridge, and you willingly put a bomb in the fridge, would you blame Samsung when your fridge explodes?

      Microsoft gives you the freedom to install software that runs with the same level of privilege as the kernel itself. You’re the one that chose to install defective software, and then give it kernel level permissions. You put a bomb in your computer and now you’re blaming Microsoft after the bomb exploded.

      Microsoft didn’t make the decision to allow the faulty input, the person who installed the software did, when they gave it permission to run in kernel mode.

    • andrew@radiation.party
      link
      fedilink
      arrow-up
      5
      ·
      2 months ago

      Because Microsoft isn’t responsible for every program that runs on their OS.

      CrowdStrike is an EDR that enterprises choose to install. The bug was caused by a dodgy content bundle update, which is something that’s meant to be 100% safe but evidently they found and triggered a bug.

    • The Cuuuuube@beehaw.org
      link
      fedilink
      English
      arrow-up
      4
      ·
      2 months ago

      Most of who got hit though was people who contracted with crowd strike directly though. Its not like Microsoft pushed crowdstrike onto people.

    • Abnorc@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      Not every enterprise runs crowdstrike, so it’s not Microsoft’s fault. I was having trouble finding out what happened because our computers were working normally, lol. The XKCD comic tipped me off.