Linux

8070 readers

63 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
Be respectful: Treat fellow community members with respect and courtesy.
Quality over quantity: Share informative and thought-provoking content.
No spam or self-promotion: Avoid excessive self-promotion or spamming.
No NSFW adult content
Follow general lemmy guidelines.

founded 1 year ago

MODERATORS

MigratingtoLemmy@lemmy.world

127

Dual booting with Windows? Beware recent Win update! (arstechnica.com)

submitted 2 months 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.

you are viewing a single comment's thread
view the rest of the comments

[–] vikingtons@lemmy.world 2 points 2 months ago (5 children)

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

[–] thanksforallthefish@literature.cafe 4 points 2 months ago (4 children)

No. Any efi dual boot is affected.

[–] vikingtons@lemmy.world 2 points 2 months ago (3 children)

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

[–] thanksforallthefish@literature.cafe 5 points 2 months ago (1 children)

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

[–] vikingtons@lemmy.world 2 points 2 months ago* (last edited 2 months ago) (1 children)

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.

[–] thanksforallthefish@literature.cafe 2 points 2 months ago

Sounds like a smart move.

load more comments (1 replies)