[personal profile] mjg59
The Microsoft Surface is a fairly attractive bit of tablet hardware, and as a result people have shown interest in running Linux on it. The immediate problem is that (like many ARM devices) it has a locked-down firmware that will only run signed binaries - unlike many other ARM devices, this is implemented using an existing standard (UEFI Secure Boot). Microsoft provide a signing service for UEFI binaries, so it's tempting to think that getting around this restriction would be as simple as taking an existing Linux bootloader, signing it and then booting. Unfortunately Microsoft's signing service signs binaries using a different key (the "Microsoft Windows UEFI Driver Publisher" key) to the one used to sign Windows, and the Surface doesn't carry that key. Booting Linux on these devices would involve finding a flaw in the firmware and using that to run arbitrary code.

Could this also be a problem on x86? In theory - Microsoft don't require that vendors carry the driver publisher key, and so a system could be Windows 8 certified and still not carry it. It's unlikely to occur in practice, though, since any third party expansion hardware will then fail on that device. As a result, anything with PCIe or Expresscard slots is effectively certain to have this key. If anyone finds any counterexamples, please let me know.

OEM laptops - not yet, but probably soon

Date: 2013-01-03 11:53 pm (UTC)
From: (Anonymous)
lenovo and HP currently use a PCI ID whitelist in their firmwares to prevent WiFi and 3G cards they didn't rebrand and sell at a markup from working in laptops they make.

I will be very surprised if they do not omit the UEFI driver signing key on some laptops and servers to force you to use only supported, authorized and conveniently marked up hardware for disk/RAID controllers, hardware iSCSI initiators, PXE-capable NICs, remote management cards (VGA+USB host interface to Ethernet and VNC), etc. The temptation of lock-in and high margins is likely to be too strong, as we've already seen with various OEM's periodic attempts to lock server hardware support to their own storage controllers.

Re: OEM laptops - not yet, but probably soon

Date: 2013-01-09 01:45 am (UTC)
From: (Anonymous)
I don't know if this is being brought up deliberately, but in case it's not, have a look here (http://web.archive.org/web/20060720082959/http://www.srcf.ucam.org/~mjg59/thinkpad/wireless.html). Note the user name in the URL ;)

Re: OEM laptops - not yet, but probably soon

Date: 2017-09-27 01:52 pm (UTC)
From: (Anonymous)
I cannot agree more. When my HP laptop's Wireless adapter is broken, I bought another 3945ABG and put it on. When I find out a msg read:"Incompatible Wireless card found! Remove and press Ctrl+Alt+Del to reboot normally", I lost my shit.

Profile

Matthew Garrett

About Matthew

Power management, mobile and firmware developer on Linux. Security developer at Aurora. Ex-biologist. [personal profile] mjg59 on Twitter. Content here should not be interpreted as the opinion of my employer. Also on Mastodon.

Page Summary

Expand Cut Tags

No cut tags