• loathsome dongeater@lemmygrad.ml
        link
        fedilink
        English
        arrow-up
        22
        ·
        4 months ago

        The issue was caused by a software that is designed to collect data from the computer and send it to a centralised location. It’s intrusive enough that it needs to run at kernel level. The issue was caused because it auto-updates itself. The recent update was borked causing the auto-update attempt to send it into a bootloop.

        It’s a software that employers install on their employees’ work computers. I don’t know exactly how this kind of spying is helpful to the employer. But if it just run in the userspace this particular problem wouldn’t have happened.

        • Addfwyn@lemmygrad.ml
          link
          fedilink
          arrow-up
          18
          ·
          4 months ago

          Funfact, we actually opt in to the feature to stay a version behind on updates, specifically to prevent this kind of thing from happening. Turns out that is a fucking lie because we still got this update.

            • Addfwyn@lemmygrad.ml
              link
              fedilink
              arrow-up
              3
              ·
              4 months ago

              They pissed off enough of the powers that be (read: corporations) that I would be surprised if they made it through this intact. I wouldn’t be surprised if they crashed and got acquired by one of the tech giants. Which I hope is the case, friendly reminder that crowdstrike was one of the key sources of all the russiagate bullshit.

    • USSR Enjoyer@lemmygrad.ml
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      4 months ago

      Better opportunity to talk about how your machines are held hostage by closed-source fascist CIAware.