Red Hat Bugzilla – Bug 834866
Last modified: 2013-04-03 13:03:59 EDT
Description of problem: Secure boot (brainstorm)
Version-Release number of selected component (if applicable): all the things
How reproducible: Try to install a Fedora install on a pc with a Microsoft Windows 8 certified motherboard.
Steps to Reproduce:
1. insert the cd
2. try to boot cd
No execution of boot cd
Be able to install my distro
Additional info (and my actual idea):
Maybe a solution to the whole Secure boot fuss: let hardware manufacturers implement some kind of restricted mode overlay uefi-popup whenever a program wants to insert a new key. (And implement specific calls for that). When such a popup would be displayed, execution of the caller would be halted, and input would go directly to the uefi popup. The user then has to confirm or reject the action by pressing 'Y' or 'N'.
I seem to remember a similar approach in the years of Windows 3.11 when some bioses provided such approach to detect virusses by the bios. (don't shoot me though, i was 9 years old at the time).
Also keep stuff bootable, but without access to non-removable disks until a valid key is found.
Where you not able to disable Secure Boot?
Secure Boot is supported in Fedora 18 and newer.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here: