"They are almost certainly going to be more secure than depending on some crazy root of trust based on a big company, with key signing authorities that trust anybody with a credit card."
Not to mention this kind of thing: https://bugzilla.mozilla.org/show_bug.cgi?id=476766
Also, when it comes to stuff this important, there is no such thing as a trusted neutral party.
The main issue with the internet model is how uncompetitive the whole thing is. You have just a few companies handing out keys and they charge upwards of $50 a year just for the "pleasure" of having secured communications.
Secure boot would likely suffer from the same problem. But yet I'd still take that over this...
It's just that, well, there's only really one software manufacturer with enough clout to get all the hardware vendors to include its key, and it's a heck of a lot easier to just get a sub-key signed by their master key than pretty much anything else.
None of the linux vendors banded together to create a NPO which would simply manage keys, ensure it was avialable to all manafacturers. Maybe even provide a logo/stamp/certification/brand so people can instantly see it's supported.
The fact that ONLY Microsoft have done this isn't really the fault of Microsoft. The fact that devs can't agree on the most elegant way of providing the chain of trust, in a manner which plays nicely is again, not Microsofts fault.
Yet Microsoft is being flamed for this.... Why exactly is this their fault?
MS is at fault for pushing this whole system. Whether Linux distros could or not join the system is a red herring.
What?!
Pushing UEFI, which isn't their design, which has been used by Apple and other for years, or pushing secure boot?
Secure Boot is a damned good idea, and whilst IANAL it appears that for a windows sticker you MUST allow it to be switched off.
So its Microsoft are in fact pressuring OEMs to ensure that people can run other OS's on their kit (except ARM).
What this is about is how the other OS's can get the benefit of SecureBoot, well, if they can't get their act together as I mentioend above, why should they fuss that someone else gets SecureBoot. Lets be hoenst too, most people who need such simple "mum proof protection" are on Windows anyway.
Although Microsoft will now point at me and say "but, but we need to prevent boot sector viruses!" it's telling that no other operating system except Windows commonly suffers from this problem.
This is an honest question, as this area isn't my specialty, but could this be for the same reason that people used to perpetuate the myth that Macs don't get viruses? Attackers simply target the platform with the largest market share.
There is nothing whatsoever stopping Linux bootkits technically. Please stop spreading FUD.
Any PKI based system is a shit idea unless you are personally in control of the trusted root CA, which in this case you're not. I think that is what Linus is saying.
Google for "certificate authority compromised" and you'll see what utter wads of shit for brains this could be entrusted to.
1. http://blog.hansenpartnership.com/owning-your-windows-8-uefi...
It should ship with no PKI/certificate scheme at all. We don't need it and it doesn't work and its blatantly obvious.
Secure boot is entirely worthless from end to end.
With UEFI secure boot, you can delete Microsoft's key and add you own.
Such as?
Should Microsoft trust WC3?
Or Foxconn trust the United Nations?
Every organization requires funding. How would this party receive it?
Because the world is unfortunately short of philosopher kings, we are probably better served by the marketplace when it comes to hardware manufacture.
No matter how you do it, it seems to have the same problems as SSL CAs and certificates (that is, some CAs are corrupt/negligent/compromised).
And in your proposal, what do you do if the root key ever gets compromised?
What was needed was for a trusted neutral party(or two) to be the owner of the root key, and for that organisation to hand out child keys (e.g. Microsoft, Open Source Initiative, Apple, etc) who could in turn generate child keys (all of which could be revoked). Essentially we need the "internet model" of key exchanges for this too.
I cannot understand who thought it was a good idea for Microsoft to be the only authorised party to generate keys. Even from Microsoft's perspective it is just asking to get anti-trust-ed again.