5 ms·
I was struck by the following passage: >including Secure Boot, which even now requires FOSS users to purchase a license from Microsoft to boot FOSS on affected
by bogomipz 10y ago
I was struck by the following passage:
>including Secure Boot, which even now requires FOSS
users to purchase a license from Microsoft to boot FOSS on affected machines that lack an appropriate Secure Boot override."
Can someone explain this to me, would this be for instance be Lenovo laptops making a deal with Microsoft since Windows is the default OS installed on these laptops? Is Microsoft mandating all OEMs/hardware vendors to configure secure boot with a MS signing key? Even if I order a laptop with no OS installed?
- wmf 10y agoIs Microsoft mandating all OEMs/hardware vendors to configure secure boot with a MS signing key? Basically yes; it's required to get the Windows sticker. I haven't heard that MS charges money to sign bootloaders, though.
- bogomipz 10y agoThanks, I have to wonder how much of bureaucratic headache that is to get your bootloader signed.
- sblom 10y agoI believe that the Windows 10 logo requirements are exactly the opposite of that. If you look at the UEFI requirements for Windows 10[1], specifically clauses 19 and 20, it says for non-ARM systems the user MUST be able to put Secure Boot into Custom signature-checking mode. [1] https://msdn.microsoft.com/windows/hardware/commercialize/design/compatibility/systems#system-fundamentals-firmware-uefisecureboot https://msdn.microsoft.com/windows/hardware/commercialize/de...
- wmf 10y agoThey're not opposites. PCs are required to have secure boot and they're required to have MS's cert installed and they're required to be able to disable secure boot.
- vedranm 10y agoThis was true in Windows 8 times, but with Windows 10 the requirement to be able to turn off Secure Boot vanished: https://arstechnica.com/information-technology/2015/03/windows-10-to-make-the-secure-boot-alt-os-lock-out-a-reality/ https://arstechnica.com/information-technology/2015/03/windo... The whole story around Secure Boot could be understood (even without a tinfoil hat) as a part of a slippery slope to lock out alternative OSes, highly recommended post: https://www.phoronix.com/forums/forum/phoronix/general-discussion/49072-new-secureboot-concerns-arise-with-windows-10?p=623687#post623687 https://www.phoronix.com/forums/forum/phoronix/general-discu...
- gizmo686 10y agoSecure boot has 4 types of keys: The signature database (db) and forbidden signature database (dbx) contain a whitelist and blacklist respectivly of keys, signatures, and hashes that are trusted to run. Updates to either of the above lists must be signed by a Key Exchange Key (KEK). Most implementations allow multiple Key Exchanges Keys. Updates to the list of Key Exchange Keys must be signed by the Platform Key (PK). Most implementations only allow 1 PK, and that PK is Microsoft's. This means that any binary run on a secure boot machine with Microsoft's PK has a chain of trust rooted at Microsoft. It may be possible to update the PK before transitioning the system to secure mode; but most consumer devices ship already in secure mode. This is different from simply disabling secure boot, which would still not allow you to update PK (for obvious reasons). EDIT: It appears that it is called "user mode" and "setup mode" instead of secure mode. Also it seems that some systems allow you to re-enter setup mode from the "bios" [0]. On an unrelated note, what do we call the firmware provided settings app now that it is no longer part of the BIOS. [0] https://wiki.gentoo.org/wiki/Sakaki%27s_EFI_Install_Guide/Configuring_Secure_Boot#Entering_Setup_Mode.2C_and_Installing_New_Keys https://wiki.gentoo.org/wiki/Sakaki%27s_EFI_Install_Guide/Co...
- bogomipz 10y agoThanks for the detailed answer. In regards to: >" Most implementations only allow 1 PK, and that PK is Microsoft's." Isn't this a bit monopolistic and coercive though? "If you want the Microsoft Hologram on your product the PK has to be has to be Microsoft and there can only be one PK." I can't believe this doesn't violate some type of anti-trust laws.
- RandomOpinion 10y agoHow so? The OEMs want to make hardware that runs Windows. Microsoft provides a specification[0] and certification suites[1] that defines what "Windows-compatible" means, which OEMs then follow. Nothing coercive about that. There is no open standard that defines what a PC is. Linux and other operating systems are piggybacking on the Windows PC standard. If they want OEMs to manufacture hardware to their standards, they'll have to create their own "Linux-compatible" specification and persuade OEMs to follow it. [0] https://msdn.microsoft.com/windows/hardware/commercialize/design/compatibility/index https://msdn.microsoft.com/windows/hardware/commercialize/de... [1] https://msdn.microsoft.com/en-us/library/windows/hardware/dn930814.aspx https://msdn.microsoft.com/en-us/library/windows/hardware/dn...
- bubblethink 10y agoI tend to think the SecureBoot isn't really a grand conspiracy. You can't realistically expect end users to be in charge of keys. So MS does what's best for itself. The problem is with poor implementations by vendors that don't support self signing, and in some cases don't even support disabling secure boot.
- bogomipz 10y ago>"You can't realistically expect end users to be in charge of keys." Not but the OEM vendors and not MS should be the owner of the sole PK allowed in the engine. MS doesn't make the hardware yet they are in charge of it. I think that's the issue, it has nothing to do with a grand conspiracy.
- pjc50 10y ago> now requires FOSS users to purchase a license from Microsoft to boot FOSS This isn't actually true, is it?
- cyphar 10y agoThey charge a fee to get a certificate that you can use to submit binaries to be signed with the Microsoft signing service. If you're a user of a distribution you won't have this problem, because distributions have already paid and have a hack "shim" which effectively enrols the distribution's own keys into the trustdb. But if you wanted to make your own distribution you would have to pay.
- jwilk 10y agoNope. It should be normally possible to disable Secure Boot. In fact, many distributions don't support Secure Boot at all.
- cyphar 10y ago> Nope. It should be normally possible to disable Secure Boot. This is only true on x86. On arm, Microsoft's requirements state that it should not be possible for users to disable Secure Boot.
- jwilk 10y agoBut is there any interesting ARM hardware that is certified for Windows? (Honest question, I have no idea.)
- cyphar 10y agoFor Windows RT, looks like there wasn't that many certified devices.[1] [1]: https://en.wikipedia.org/wiki/Windows_RT#Devices https://en.wikipedia.org/wiki/Windows_RT#Devices