All our servers and company laptops went down at pretty much the same time. Laptops have been bootlooping to blue screen of death. It’s all very exciting, personally, as someone not responsible for fixing it.

Apparently caused by a bad CrowdStrike update.

Edit: now being told we (who almost all generally work from home) need to come into the office Monday as they can only apply the fix in-person. We’ll see if that changes over the weekend…

  • StV2@lemmy.world
    link
    fedilink
    English
    arrow-up
    32
    arrow-down
    1
    ·
    3 months ago

    It’s disappointing that the fix is so easy to perform and yet it’ll almost certainly keep a lot of infrastructure down for hours because a majority of people seem too scared to try to fix anything on their own machine (or aren’t trusted to so they can’t even if they know how)

    • HaleHirsute@infosec.pub
      link
      fedilink
      English
      arrow-up
      38
      ·
      3 months ago

      They also gotta get the fix through a trusted channel and not randomly on the internet. (No offense to the person that gave the info, it’s maybe correct but you never know)

      • kadotux@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        8
        ·
        3 months ago

        Yeah, and it’s unknown if CS is active after the workaround or not (source: hackernews commentator)

      • letsgo@lemm.ee
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 months ago

        True, but knowing what the fix might be means you can Google it and see what comes back. It was on StackOverflow for example, but at the time of this comment has been taken offline for moderation - whatever that means.

    • NaibofTabr@infosec.pub
      link
      fedilink
      English
      arrow-up
      24
      ·
      3 months ago

      This sort of fix might not be accessible to a lot of employees who don’t have admin access on their company laptops, and if the laptop can’t be accessed remotely by IT then the options are very limited. Trying to walk a lot of nontechnical users through this over the phone won’t go very well.

      • AccountMaker@slrpnk.net
        link
        fedilink
        English
        arrow-up
        6
        ·
        3 months ago

        Yup, that’s me. We booted into safe mode, tried navigating into the CrowdStrike folder and boom: permission denied.

    • thehatfox@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      edit-2
      3 months ago

      Might seem easy to someone with a technical background. But the last thing businesses want to be doing is telling average end users to boot into safe mode and start deleting system files.

      If that started happening en masse we would quickly end up with far more problems than we started with. Plenty of users would end up deleting system32 entirely or something else equally damaging.

    • r00ty@kbin.life
      link
      fedilink
      arrow-up
      9
      ·
      3 months ago

      It might not even be that. A lot of places have many servers (and even more virtual servers) running crowdstrike. Some places also seem to have it on endpoints too.

      That’s a lot of machines to manually fix.