Language Selection

English French German Italian Portuguese Spanish

Microsoft confirms UEFI fears, locks down ARM devices

Filed under
Linux
Microsoft
Legal

At the beginning of December, we warned the Copyright Office that operating system vendors would use UEFI secure boot anticompetitively, by colluding with hardware partners to exclude alternative operating systems. As Glyn Moody points out, Microsoft has wasted no time in revising its Windows Hardware Certification Requirements to effectively ban most alternative operating systems on ARM-based devices that ship with Windows 8.

The Certification Requirements define (on page 116) a "custom" secure boot mode, in which a physically present user can add signatures for alternative operating systems to the system's signature database, allowing the system to boot those operating systems. But for ARM devices, Custom Mode is prohibited: "On an ARM system, it is forbidden to enable Custom Mode. Only Standard Mode may be enable." [sic] Nor will users have the choice to simply disable secure boot, as they will on non-ARM systems: "Disabling Secure [Boot] MUST NOT be possible on ARM systems." [sic] Between these two requirements, any ARM device that ships with Windows 8 will never run another operating system, unless it is signed with a preloaded key or a security exploit is found that enables users to circumvent secure boot.

Rest here

Also: Is Microsoft Blocking Linux Booting on ARM Hardware?




Shame on you Microsoft

They should be ashamed of themselves for the way they act. It would be nice if the OEMs would tell MS to go stick it where the Sun don't shine.

Who Cares

All this means is that Microsoft will be heavily subsidizing certain ARM devices, and they're protecting their investment (just like Cell Phone Carriers do).

As with cell phones, there will be un-locked ARM devices available, just not at dirt cheap subsidized prices.

Nothing to get your panties in a knot over.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

PC-MOS/386 is the latest obsolete operating system to open source on Github

PC-MOS/386 was first announced by The Software Link in 1986 and was released in early 1987. It was capable of working on any x86 computer (though the Intel 80386 was its target market). However, some later chips became incompatible because they didn't have the necessary memory management unit. It had a dedicated following but also contained a couple of design flaws that made it slow and/or expensive to run. Add to that the fact it had a Y2K bug that manifested on 31 July 2012, after which any files created wouldn't work, and it's not surprising that it didn't become the gold standard. The last copyright date listed is 1992, although some users have claimed to be using it far longer. Read more

GIMP, More Awesome Than I Remember

For what seems like decades, GIMP (Graphic Image Manipulation Program) has been the de facto standard image editor for Linux. It works well, has many features, and it even supports scripting. I always have found it a bit clumsy, however, and I preferred using something else for day-to-day work. I recently had the pleasure of sitting at a computer without an image editor though, so I figured I'd give GIMP another try on a non-Linux operating system. See, the last time I tried to use GIMP on OS X, it required non-standard libraries and home-brew adding. Now, if you head over to the GIMP site, you can download a fully native version of GIMP for Windows, OS X and Linux. Read more

Linux 4.13.9

I'm announcing the release of the 4.13.9 kernel. All users of the 4.13 kernel series must upgrade. The updated 4.13.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.13.y and can be browsed at the normal kernel.org git web browser: http://git.kernel.org/?p=linux/kernel/git/stable/linux-st... Read more Also: Linux 4.9.58 Linux 4.4.94 Linux 3.18.77

Linux 4.14-rc6

So rc6 is delayed, not because of any development problems, but simply because the internet was horribly bad my usual Sunday afternoon time, and I decided not to even try to fight it. And by delaying things, I got a couple more ull requests in from Greg. Yay, I guess? rc6 is a bit larger than I was hoping for, and I'm not sure whether that is a sign that we _will_ need an rc8 after all this release (which wouldn't be horribly surprising), or whether it's simply due to timing. I'm going to leave that open for now, so just know that rc8 _may_ happen. Read more Also: Linux 4.14-rc6 Released: Linux 4.14 Kernel Final In 2~3 Weeks