4 ms·
You can disable secure boot in the "BIOS" I had the same worry, some 15 years ago I think it was the top of the "they're trying to lock PCs down 100%". Today I
by raverbashing 7y ago
You can disable secure boot in the "BIOS"
I had the same worry, some 15 years ago I think it was the top of the "they're trying to lock PCs down 100%". Today I don't worry so much
- Boulth 7y agoExactly. Additionally Microsoft requires vendors to allow disabling Secure Boot on x86 (not so on ARM). I'm on mobile so excuse me the lack of source link.
- zahllos 7y agoThey also require the ability to change the keys. It's part of the Windows Hardware Certification Kit, previously Logo Kit. See https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-secure-boot-key-creation-and-management-guidance https://docs.microsoft.com/en-us/windows-hardware/manufactur...
- 0xffff2 7y agoThat's really strange, because last time I tried to get Arch up and running on my Surface Pro 4, I couldn't find any way to change the keys on it.
- zahllos 7y agoIt's not always easy to do (and Microsoft could always exempt themselves from surface devices) - I think the spec only requires that it is possible, not that there is a nice dialog box in the bootloader to do it (unfortunately). You need to put the device into setup mode first, which should be possible by disabling secure boot then deleting the platform key. Then you can update the DB, then KEK and finally PK using keytool.efi. There's many guides on the process, see for example: https://blog.hansenpartnership.com/owning-your-windows-8-uefi-platform/ https://blog.hansenpartnership.com/owning-your-windows-8-uef... and https://www.rodsbooks.com/efi-bootloaders/controlling-sb.html https://www.rodsbooks.com/efi-bootloaders/controlling-sb.htm.... Specifically, what I'd do is: disable secure boot, copy shell.efi and keytool to the ESP, add a boot entry for the shell.efi entry, always useful, then boot to it, run keytool, clear the PK - voila you are in setup mode and should be able to change everything. Be aware that once you set a platform key, updates to any key database are checked for valid signatures. Updates to the KEK must be signed by PK, updates to the DB, DBX must be signed by the KEK, etc. If there's no dialog, you might also want to back up the keys, if you want to set the machine back to its factory default setting. I can imagine Microsoft might not have enabled this level of control for their surface devices, although as I understand their HCK, they should. Perhaps they exempt themselves :(
- djsumdog 7y agoI think people have broken UEFI+ARM. I've seen posts about running Linux on the older Windows mobile devices. The bigger problem is none of the hardware has any OSS driver support, so even if you can get a different OS to boot, you still can't use things like Wi-Fi/BT/video acceleration.
- swebs 7y agoFrom what I hear, Apple tries extremely hard to block Linux from booting on new Macbook models. Disabling "secure boot" isn't enough.
- derefr 7y agoI find it strange that they bother, since in the end you can always just run a fullscreen Linux VM and hand it over 99% of the computer’s resources. Maybe Apple’s true worry might be revealed by considering the difference between what they allow and what they prevent. Apple allow you to have a wholly-Linux UX on an Apple laptop; but they don’t allow Linux developers to run a Linux kernel directly on Apple hardware. Maybe what they’re really concerned about is Linux having an easy testbed for developing MacBook hardware/peripheral drivers, such as for the T2, such that people could build apps in other OSes that take advantage of the touchbar, and thus in some way “commoditize” one of the costlier USPs of macOS?
- umanwizard 7y agoThey actually don't prevent you from running a Linux kernel on their hardware, though.
- deleted 7y ago[deleted]
- saagarjha 7y agoPeople are making software for the Touch Bar that runs on Windows already.
- xenadu02 7y agoIf a minuscule number of people buying your hardware ever run linux, would you waste even one week testing support for it? Would you waste even a single EFI engineer's time on it? What if it were 0.1%? Or 0.01%? What leads you to believe anyone at Apple spent even 5 minutes thinking about linux support at any point in time?
- 7y ago