Already got you? this article tells you how you can fix it.

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

    Am I right in assuming this only applies to single disks partitioned with both Windows and a Linux distro?

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

        Even separate disks? Ouch. I’m guessing Fedora is not impacted here.

        • thanksforallthefish
          link
          fedilink
          English
          arrow-up
          4
          ·
          3 months ago

          Yes. Separate or single disks makes no difference, it writes changes to the efi partition that bios references to boot.

          I don’t know whether fedora is impacted, the article specifies the following as documented impacts

          " The reports indicate that multiple distributions, including Debian, Ubuntu, Linux Mint, Zorin OS, and Puppy Linux, are all affected."

          And I also note that at least 2 arch implementations are impacted in addition to that list (i first saw it on arch forums).

          I would suggest you definitely DON’T assume fedora is unaffected until you check your install, fedora participates in safeboot so given all the article listed distros also do (and arch has a method for it)

          Odds are they’re impacted, M$ has done a scattergun on this, the only ones you can be sure are unaffected are those still bios booting rather than uefi

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

            Appreciate the heads up. I don’t have a particular need for secureboot on the workstation I have in mind so I suppose I can just leave that disabled for now.