Home Business IT Open Source Mageia will take time to support secure boot

Mageia, the fork of the popular Mandriva GNU/Linux distribution, has made no plans to include support for secure boot in version 3, which is now in its second beta, the project says.

The fork took place in September 2010.

A Mageia spokesperson told iTWire, in response to an inquiry, that there was a plan to include it as a discussion point when planning features for version 4.

At that point, "we will decide then how we will deal with it," the spokesperson said.

Secure boot is a feature of the Unified Extensible Firmware Interface that has replaced the BIOS.

Microsoft has implemented it and made it compulsory for any hardware that needs to be certified for Windows 8. During the boot process, there is an exchange of cryptographic keys to ensure that the kernel being booted is indeed what it claims to be.

As a result, any GNU/Linux distribution that wants to have a bootable CD or DVD for such hardware will need to support secure boot.

Red Hat's Fedora project and Ubuntu have released images that support secure boot. But there are other issues with these releases which prevent straightforward installation on secure boot-enabled systems.

WEBINAR 7th May 11am - WOW 802.11

Learn how Ruckus Redefines High-Speed, High Capacity Wi-Fi with Industry’s First 802.11ac Wave 2 Access Point

THIS IS ONE NOT TO MISS SO REGISTER NOW

DON'T MISS OUT - REGISTER NOW!

FREE - SYDNEY & MELBOURNE BUSINESS INTELLIGENCE EVENTS

The Holy Grail of the Business Intelligence (BI) industry – pervasive deployments and widespread end-user adoption – has remained an illusive dream for years. Until now!

REGISTER & SECURE YOU PLACE / BRING A FRIEND

Melbourne - venue Captain Melville’s CBD 2:30 – 6:00pm, Tuesday 28th April

Sydney - venue Redoak CBD 2:30 – 6:00pm, Thursday 30th April

DON'T MISS OUT - MELBOURNE REGISTER NOW!

DON'T MISS OUT - SYDNEY REGISTER NOW!

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