586
CrowdStrike broke Debian and Rocky Linux months ago, but no one noticed (www.neowin.net)
submitted 2 years ago by to c/technology@lemmy.world
79 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 82 points 2 years ago (3 children)

Additionally, organizations should approach CrowdStrike updates with caution

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

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] 46 points 2 years 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 before each update, with the exception of a couple machines. It's stupid that he has to do this but hey, his network was unaffected

  • permalink
  • fedilink
  • source
  • parent
  • [–] 8 points 2 years ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 16 points 2 years ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 2 years ago (2 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 26 points 2 years ago (3 children)

    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.)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 22 points 2 years ago

    Found this post that explains what happened in detail: https://lemmy.ohaa.xyz/post/3522666

    As an application developer (rather than someone who can/does code operating systems) I was just left open-mouthed …

    Looks like they’re delivering “code as content” to get around the rigour of getting an updated driver authorised by MS. I realise they can’t wait too long for driver approval for antivirus releases but surely - surely - you have an ironclad QA process if you’re playing with fire like this.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 2 years ago (2 children)

    Do you know if the sensor update policy had been set to N-2 would this have avoided the issue?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 7 points 2 years ago (1 child)

    Setting the update policy to N-2 (or any other configuration) would not have avoided the issue. The Falcon sensor itself wasn’t updated, which is what the update policy controls. As it turns out, you cannot control the content channel updates - you simply always get the updates.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •