▲ 128 ▼ Dual booting with Windows? Beware recent Win update! (arstechnica.com) submitted 2 years ago by kalkulat@lemmy.world to c/linux@lemmy.world 15 comments fedilink hide all child comments Already got you? this article tells you how you can fix it.
[–] vikingtons@lemmy.world 2 points 2 years ago (1 child) Even separate disks? Ouch. I'm guessing Fedora is not impacted here. permalink fedilink source parent hideshow 2 child comments replies: [–] thanksforallthefish@literature.cafe 5 points 2 years ago (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] vikingtons@lemmy.world 2 points 2 years ago* (last edited 2 years ago) (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] thanksforallthefish@literature.cafe 2 points 2 years ago Sounds like a smart move. permalink fedilink source parent
[–] thanksforallthefish@literature.cafe 5 points 2 years ago (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] vikingtons@lemmy.world 2 points 2 years ago* (last edited 2 years ago) (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] thanksforallthefish@literature.cafe 2 points 2 years ago Sounds like a smart move. permalink fedilink source parent
[–] vikingtons@lemmy.world 2 points 2 years ago* (last edited 2 years ago) (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] thanksforallthefish@literature.cafe 2 points 2 years ago Sounds like a smart move. permalink fedilink source parent
[–] thanksforallthefish@literature.cafe 2 points 2 years ago Sounds like a smart move. permalink fedilink source parent