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

quinkin@lemmy.world ⁨1⁩ ⁨month⁩ ago

• ISOmorph@feddit.org ⁨1⁩ ⁨month⁩ ago

  I read on another thread that an admin was emulating a testing environment by blocking CrowdStrike IPs on their firewall for the whole network, with the exception of a couple machines to test each update. It’s stupid that he has to do this but hey, his network was unaffected

  source
• AlecSadler@sh.itjust.works ⁨1⁩ ⁨month⁩ ago

  Serious question, can you not? There isn’t an option to…like…set a review system first?

  source

  • EncryptKeeper@lemmy.world ⁨1⁩ ⁨month⁩ ago

    For antivirus definitions? No, and you wouldn’t want to.

    source

    • AlecSadler@sh.itjust.works ⁨1⁩ ⁨month⁩ ago

      But it sounds like this added files / drivers or something, not just antivirus rules?

      source

      • SeeJayEmm@lemmy.procrastinati.org ⁨1⁩ ⁨month⁩ ago

        Turns out it was a content update that caused the driver to crash but the update itself wasn’t a driver (as per their latest update.)

        source

        • -> View More Comments
      • mox@lemmy.sdf.org ⁨1⁩ ⁨month⁩ ago

        nitter.poast.org/…/1814343502886477857

        source
• corsicanguppy@lemmy.ca ⁨1⁩ ⁨month⁩ ago

  We would if we were able to control their “deployable content”.

  Minimum safe distance.

  source