On 11/12/2012 1:35 PM, Greg KH wrote:
On Mon, Nov 12, 2012 at 04:00:11AM -0800, Linda Walsh wrote:
Michael Schroeder wrote:
On Thu, Nov 08, 2012 at 06:41:03PM +0100, Stefan Dirsch wrote:
This is *not* a bug, but an intentional change. ;-) The GLUE layer is now built on the target system.
Uh, doesn't that conflict with the new UEFI secure boot where all kernel modules have to be signed?
Cheers, Michael.
Secure boot is for HW vendors who want to turn PC's into locked-down pieces of HW that are only upgrade-able at the vendors' discretion.
Not at all, I want secure boot for my systems, with a key that I have control over, to ensure that no one else has installed a boot loader on it that I do not know about.
For that reason alone, you should want it as well.
I got a heads-up on this due to a faulty UEFI bios that occasionally complains about my not having a license to upgrade my memory configuration (which my Dell machine doesn't 'currently' need), but in the future, the UEFI Bios will allow the vendor have a lock on what HW you can put into your computer and have it boot as well as what SW.
No, not at all, you have control over this, you can put your own keys in the BIOS just fine.
It's in the spec that the user can manage keys, and vendors have an impeccable history of implementing specs fully and correctly instead of just enough to satisfy Windows. That's why acpi was never a problem for anyone for instance. MS, Apple, large hardware vendors, they're all honest nice considerate principled guys who would never use their position to limit your options in their benefit. That's why vendor lock-in is a term I had to invent just now because no one ever did it for real. And if they do, well, small guys with principles can make hardware just as good and just as cheap as the big guys. Those System76 laptops are just as good as a macbook or a vaio. -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org