3 ms·
>1) You can turn it off if the OEM gives you the option to, and OEMs are under no obligation to do so; and Wrong. >Mandatory. Enable/Disable Secure Boot. On n
by zokier 14y ago
>1) You can turn it off if the OEM gives you the option to, and OEMs are under no obligation to do so; and
Wrong.
>Mandatory. Enable/Disable Secure Boot. On non-ARM systems, it is required to implement the ability to disable Secure Boot via firmware setup. A physically present user must be allowed to disable Secure Boot via firmware setup without possession of PKpriv. A Windows Server may also disable Secure Boot remotely using a strongly authenticated (preferably public-key based) out-of-band management connection, such as to a baseboard management controller or service processor. Programmatic disabling of Secure Boot either during Boot Services or after exiting EFI Boot Services MUST NOT be possible. Disabling Secure Boot must not be possible on ARM systems.
Source:
Windows Hardware Certification requirements
http://msdn.microsoft.com/en-us/library/windows/hardware/jj128256 http://msdn.microsoft.com/en-us/library/windows/hardware/jj1...
- smacktoward 14y agoWell that's a relief! My recollection was based on the last burst of news coverage on the issue late last year; it sounds like Linux vendors like Red Hat worked with Microsoft on the issue between now and then (Red Hat this month: "the Linux Foundation, hardware partners, and Microsoft to collaboratively develop a UEFI secure boot mechanism that allows user/customer choice and ease of use" -- http://www.redhat.com/about/news/archive/2012/6/uefi-secure-boot http://www.redhat.com/about/news/archive/2012/6/uefi-secure-...), so it may be that the ambiguity was present in older MS certification specs but got cleared up later on...
- japhyr 14y agoDoes this mean you'd just toggle a BIOS setting to disable secure booting?
- zokier 14y agos/BIOS/UEFI/ Yes, that is exactly what it means.