06.09.12
Red Hat Criticised for Advancing Microsoft’s UEFI Agenda
Customers? What about users?
Summary: Bloggers sound off and rant about what Red Hat has done
IT HAS not been a good week for software freedom. Canonical gave Microsoft more control over GNU/Linux and rather than file a formal complaint (e.g. antitrust) about Microsoft’s trap Red Hat decided to dive right into it.
One Free software-aware journalist calls this a “bad idea”:
In November 2006, when Novell signed a patent licensing deal with Microsoft, the free and open source software community, for the most part, was predictably appalled.
But recently when Red Hat announced that it had signed a deal with Microsoft to ensure that Linux could be installed on PCs that were Windows 8-capable – in other words, those that supported secure boot – there was very little outcry. Red Hat is now trying to justify this act.
In Novell’s case, it was a last-ditch – albeit foolish – attempt to try and revive its business. After a series of unwise decisions that saw it lose its number-one position in the networking business (and yes, Microsoft, took it for a ride during those days), Novell had come to the point where it was willing to try anything. SUSE Linux was looked upon as some kind of saviour after Novell bought the company in 2003 but battles between suits and geeks ensured that neither party’s tactics were implemented.
Hence Novell got into bed with Microsoft. One of Novell’s best and brightest, Jeremy Allison, found the atmosphere suffocating and left the company in disgust, ending up later at Google.
But after Red Hat announced its Judas Iscariot act recently, the scenario is very different. Hell, we even have the announcement of the deal being made by the wispy-thin Matthew Garrett, once a renowned flame-master on mailing lists, but now one of the best and brightest at Red Hat, one who pledges allegiance to peace, civility, diversity, and probably the Dalai Lama too.
Carla from LXer (and former editor of Linux Today, book author, contributor to Linux.com etc.) is also upset about what Red Hat has done. To quote:
Tim Burke of Red Hat wrote a masterful apologetic for Microsoft’s strong-arming and takeover of the most basic operation of a computer– starting it up. Executive summary: We are in this 100% with our good friends in Redmond.
Allow me to hit the high points:
“One security threat that has been getting a lot of interest lately is the ability to ensure the integrity of the early boot sequence”
Only because the richest software company on the planet is utterly incompetent, and incapable of building a secure operating system. So instead they bully the rest of the world into trying to mitigate the security disaster that is Microsoft Windows.
“The mechanism used to confirm the integrity of operating system software…uses traditional key signing and variations of checksumming… Performing the checks early is crucial as it provides a safe, verified starting point.”
ORLY? Key signing is the answer, eh? Oopsie, no it isn’t, as the Flame malware proves. Flame spoofs Microsoft’s own Certificate Authority, takes over Windows Update, and fools Windows computers into thinking they’re installing genuine proven-trusted signed Microsoft code. See:
Microsoft Security Advisory (2718704) Unauthorized Digital Certificates Could Allow Spoofing
Flame malware mimics a Windows update
Flame Malware Hijacks Windows Update Mechanism
Those wacky malwares, don’t they read Microsoft press releases on how Microsoft realio trulio this time for real has made Windows like all secure?
This is not the first time that we write about this annoying move from Red Hat, but it’s good to see that other than apologies from Fedora members and Red Hat employees we mostly found opposition to Red Hat’s move. We praised Red Hat many times before (I recently interviewed their CEO), but not everything this company does is praiseworthy. Microsoft got its way and Red Hat staff seeks to justify what Red Hat has done. To quote:
The other complaint about UEFI Secure Boot is that it doesn’t add any security. There’s two aspects to this – people either think it’ll be quickly broken, or people think that the public availability of signing services will render it useless.
There are many other reasons — better reasons — to altogether reject UEFI, such as hardware obsolescence, control by Microsoft, and so on. It’s probably too late for Red Hat to retract and change course. Redmond residents who work for Microsoft are probably opening a bottle of champagne this week. █
finalzone said,
June 9, 2012 at 1:45 pm
The problem is not only Microsoft but the OEM and complicity of the US government. What Red Hat did is for survival inside the landscape mess. Remember Red Hat is a public trade company and depends from the US government requirement. Also read caitlyn’s post http://lxer.com/module/forums/t/33399/
Dr. Roy Schestowitz Reply:
June 10th, 2012 at 5:30 am
UEFI is mainly about desktop usage. RHEL is mainly a server platform (e.g. in the US government).
finalzone Reply:
June 10th, 2012 at 11:06 am
Not only server, Red Hat Enterprise Linux is also offered in enterprise/corporate desktop and workstation version:
https://www.redhat.com/apps/store/desktop/
Otherwise, why investing on applications like NetworkManager and Gnome 3 those have nothing to do with server?
Dr. Roy Schestowitz Reply:
June 10th, 2012 at 11:14 am
Some sysadmins install and use the GUI.
finalzone Reply:
June 10th, 2012 at 5:56 pm
“Some sysadmins install and use the GUI.”
True, servers can be used with GUI. The point about Red Hat providing both Desktop and Workstation for both corporations and enterprises still stands.
twitter Reply:
June 10th, 2012 at 2:15 pm
Being locked out of commodity hardware will hurt Red Hat as much as it hurts everyone else. In updates, Carla points out that gnu/linux users should have called Microsoft’s bluff. Red Hat users buy lots of hardware, they should all avoid Microsoft’s new BIOS and buy something better, like Core Boot, as advocated by the FSF.