Re: Windows Secure Boot certificate expiration (June 2026)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Once upon a time, Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> said:
> On Wed, 2025-07-09 at 20:10 -0400, Sam Varshavchik wrote:
> > Chris Murphy writes:
> > 
> > > I'm able to fix this with efibootmgr, but... what a swig of sour milk.
> > 
> > That pretty much describes my kneejerk reaction about a decade ago when I  
> > first read about secure boot, and how great it is to have each boot stage  
> > signed by an all-mighty cert.
> 
> Nothing Chris wrote about actually has anything to do with Secure Boot,
> really. It's just about how the UEFI boot manager works.

Different Chris, but... it sounds like Windows gets a "fallback"
position for when the firmware has no boot entries; is there a way to
get Fedora into that position instead (in a dual-boot setup)?  Or is it
a case of the firmware just explicitly looking for the Windows loader?

-- 
Chris Adams <linux@xxxxxxxxxxx>
-- 
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux