Home opinion-and-analysis Open Sauce 'Secure' boot: Ubuntu goes one worse than Red Hat

Author's Opinion

The views in this column are those of the author and do not necessarily reflect the views of iTWire.

Have your say and comment below.

But GRUB2 does not figure in Ubuntu's method. There will be some other bootloader, under an unspecified licence. Canonical's reasoning is that if some manufacturer were to sell a machine running Ubuntu with secure boot enabled, then if a user wanted to disable it, or run modified software, the Ubuntu specific key would have to be revealed because of the terms of the GRUB2 licence.

The Free Software Foundation has pointed out that this is a fallacy; in such a situation, the hardware distributor would be the entity that has to provide the necessary information so that the buyer can run modified software. But is Canonical listening? I doubt.

In both methods, advocated by Red Hat and Canonical, one is dependent on Microsoft. A convicted monopolist, the company is famous for making little tweaks to things so that competitors' products become unusable. But both Red Hat and Canonical seem comfortable with snuggling under the same blanket as Microsoft.

It is unlikely that Ubuntu will change; the company has a rather mulish approach to suggestions from the community and while it has been at pains to emphasise the community aspect over the commercial, in reality this is mere spin.

The departure from co-operation with the rest of the GNU/Linux community is not unique for Canonical. Its distribution, which would not exist were it not for the excellent work of the Debian GNU/Linux developers, and to which it contributes very little upstream, does not even carry the Linux name. No, it is just plain Ubuntu.

The other better-known distributions like OpenSUSE and Debian are yet to announce their plans for dealing with Microsoft's ruse. But when the billion-dollar outfit, Red Hat, leads the way in paying homage, it would be difficult for community projects to adopt solutions which are from left field.

 

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

Sam Varghese

website statistics

A professional journalist with decades of experience, Sam for nine years used DOS and then Windows, which led him to start experimenting with GNU/Linux in 1998. Since then he has written widely about the use of both free and open source software, and the people behind the code. His personal blog is titled Irregular Expression.

Connect