http://mjg59.dreamwidth.org/12745.html
Translation: As long as PC OEMs are putting out mobo's with UEFI burned in there is no way to overwrite it with Coreboot.
What would be needed is a mobo maker who burned Coreboot or made a mobo which allowed retailers to burn Coreboot on a naked EPROM. Only one out of a million users could burn Coreboot onto a naked EPROM, IF they had an EPROM burner.
Why not just avoid the entire Secure Boot problem by using Coreboot? Because the reason we have the Secure Boot problem is because Microsoft's Windows 8 certification requirements mean vendors have to ship a UEFI implementation with Secure Boot. You could satisfy that by using Coreboot with a Tiano payload, but it'll still have Secure Boot enabled so you still have the same set of problems. But maybe you could just reflash your system with Coreboot? No, because another part of the requirements states that all firmware updates have to be cryptographically signed now. The only way to reflash will be to attach a flash programmer directly to your motherboard.
So why not just use Coreboot? Because it doesn't help solve this problem in any way.
So why not just use Coreboot? Because it doesn't help solve this problem in any way.
What would be needed is a mobo maker who burned Coreboot or made a mobo which allowed retailers to burn Coreboot on a naked EPROM. Only one out of a million users could burn Coreboot onto a naked EPROM, IF they had an EPROM burner.
Comment