On Fri, Mar 27, 2015 at 4:22 PM, Dave Ihnat <dihnat@xxxxxxxxxx> wrote: > On Fri, Mar 27, 2015 at 05:30:41PM -0400, Mickey wrote: >> Is this true with Linux, Fedora ? I though Secure Boot was overcome >> as a problem. > > I've been watching this, and the concern are threefold. > > First, Microsoft previously had required that manufacturers make > SecureBoot and UEFI optional; For pre-loaded systems, UEFI is mandatory, as is SecureBoot enabled by default, as is a user accessible toggle to disable it. > The final issue is that to date, it's been required to allow users to > manage the keys used for SecureBoot, adding their own as they deem fit. > Currently, it's unclear if that requirement will stand. So far that appears to be unchanged. A bit of a concern is this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1170245 It's possible for a user to have a Windows 10 system, be unable to disable Secure Boot, unable to boot Windows (because of this bug) from the GRUB menu, and have a system that doesn't provide access to firmware setup or one-time boot menu via an F key at startup time. So they'll have to learn how to enable firmware setup access from Windows, and reboot, at which point now the user must learn how to change the boot order using efibootmgr via CLI since there isn't a GUI boot manager. Kinda, ick. But shortly after Windows 10 is released, we'll see Fedora 23 which should have the bug fixed at the latest. -- Chris Murphy -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
