I wanted to write about the Linux boot and UEFI from a while now, but I figured out is better to learn first more about the issue and take a deep breath before taking a position. In the meantime, many faces of the debate were talked in various places, so I think I have a better grasp.
From the beginning, when people started talking about Secure Boot some warned about the treat to Free Software, but they were pretty much dismissed by many as a bunch of hippies following the smelly RMS, we'll surely find a way around when will get to it. Now, after mjg wrote a long technical pieces about the struggles of making Fedora boot on UEFI with Secure Boot enabled, we can the alarmists were right and Microsoft managed to give a fatal blow to Free Software on the desktop with the help of many hardware manufacturers.
The problem is Free Software won't be able to co-exist with Windows and keep its freedom, people will have to make the choice: break-up totally with Windows (really hard in the computing landscape of today) or give away one of the fundamental freedoms granted by GPL (modify and distribute the software). Sure, this is not a problem in the server world, where you can safely turn Secure Boot off and live happily (boot malware does not affect Linux) as this is not a problem in the enterprise desktop in the places where the game is Linux-only. It is a problem in the hobbyist space, where people play with different stuff all the time and is a problem with adoption, when new potential users will have their computers locked to Windows. It is also not a Linux problem, is a Free Software problem, if you give away freedoms, you can still run Linux.
I can see how people wanting to run Linux and Windows 8 (let aside me not understanding why anyone would want to use Windows 8, it's a turd, from the same category with GNOME Shell, a tabled interface shoehorned into a desktop) will enter BIOS(UEFI) at every boot and change the Secure Boot flag according with the OS they are going to start (time wasting and annoying). And you will have to turn it off, don't expect things like drivers or kernel modules from RPM fusion or similar sources to receive certificates, after all they distribute software with legal restrictions in the US, the home of the certification authority.
So short term disable Secure Boot, keep Windows 7 if you have to dual boot, put your own keys inside BIOS(UEFI), pay, there seem to be some solutions. How about long term? I expect "pirates" will crack Windows 8 anyway and make it boot without Secure Boot. Then, in one or two releases Microsoft will change the logo specifications, Secure Boot will be mandatory with no BIOS option to turn it off - we must defend ourselves from evil pirates and malware writers and over 90% of the computers, "designed for Windows", will be unable to run a Free Software operating system (Linux desktop is busy chasing windmills with user interface experiments, so it won't gain significant market share).
My prevision is even more grim: by that time Windows will move to allowing installs only from the "app store" and Free Software applications will be out (remember, apps like Firefox, LibreOffice or even GIMP have the bulk of the users on Windows). By that time Free Software will be dead and buried, wanting a Microsoft alternative we will have the choice of Google Chrome with everything in the "cloud".
Quite negative so far, right? There should be a solution I see... yes, I think the Free Software world should refuse Microsoft's proposal for Secure Boot. Some FOSS developers argue having a secure boot process can be a good thing, while they may be right, here is not the case, Microsoft proposal is broken by design, we should not endorse it, join the opposition and get the anti-trust regulators to make something, all while teaching people how to change BIOS settings and generate and install own keys. I don't see any important player endorsing the FSF petition: Fedora is not there, Red Hat is not there, Debian is not there, Canonical is not there, Ubuntu is not there, Mint is not there... not any distro is there. And this is a bad thing.