• gwindli@lemy.lol
    link
    fedilink
    arrow-up
    1
    ·
    4 months ago

    there’s an easy fix. it could be done with a single boot attempt if M$ hadnt made it so needlessly difficult to enter safe mode

    • Norgur@fedia.io
      link
      fedilink
      arrow-up
      2
      ·
      4 months ago

      Many of the machines in question will have safe mode walled off for security reasons anyway.

      • gwindli@lemy.lol
        link
        fedilink
        arrow-up
        0
        ·
        4 months ago

        fair enough. i can see that disabling safe mode would be a decent security measure. but by the time that kind of exploit is used, you’ve already got bad actors inside your network and there are much easier methods available to pivot to other devices and accounts.

          • Scary le Poo@beehaw.org
            link
            fedilink
            arrow-up
            1
            ·
            4 months ago

            Well then obviously you could opt to restrict safe mode on laptops only, or laptops and desktops allowing you to get your server infrastructure up quickly so at least the back end is running properly.

            Ffs.

            • jarfil@beehaw.org
              link
              fedilink
              arrow-up
              1
              ·
              4 months ago

              Servers with KVM access, could have it compromised, letting bad actors enter safe mode.

                • jarfil@beehaw.org
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  4 months ago

                  Doesn’t need to be fully compromised, but it isn’t unusual for the access credentials to some portion, to be stored on an easier to compromise system. Disabling safe mode on a server, prevents stuff like a single compromised laptop, from becoming a full server compromise.