On Sat, 2019-12-28 at 16:36 -0700, Chris Murphy wrote:
I'm noticing the only release criterion that has secure boot
listed is
an exception for Windows dual booting that I think is obsolete:
https://fedoraproject.org/wiki/Fedora_32_Final_Release_Criteria#Windows_d...
The bootloader entry part of this criterion does not apply when Secure
Boot is enabled (because it has not yet been made to work, and fixing
it is not trivial). cases.
I ran into that while trying to find a criterion for this bug being a blocker:
https://bugzilla.redhat.com/show_bug.cgi?id=1782778
It's mentioned in the footnotes for the 'Release-blocking images must
boot' criterion in Basic:
https://fedoraproject.org/wiki/Basic_Release_Criteria#Release-blocking_im...
"Supported firmware types
Release-blocking images must boot from all system firmware types that
are commonly found on the primary architectures. For the x86_64
architecture, UEFI with Secure Boot configured in accordance with
Microsoft's Windows certification requirements is considered a
'commonly found' firmware type."
The 'installer requirements' header then mentions:
"Except where otherwise specified, each of these requirements applies
to all supported configurations described above."
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net