Re: Secure boot
Pau Garcia i Quiles <[email protected]>
| Newsgroups | gmane.comp.kde.events |
|---|---|
| Message-ID | <CAKcBokskExk3WdHrcUJc-gYp5ggvb8vB9d2H_xzxkj3_g0yYFw__12831.5463000492$1319125258$gmane$org@mail.gmail.com> |
> From your blogpost... > "Given that there is no Secure Boot Certification Authority, Microsoft > asked BIOS (UEFI) developers and manufacturers to include their > certificates, which looks 100% logical to me. The fact that Linux > distributions do not have such power is unfortunate, but it is not > Microsoft’s fault at all." > > It is just an accident. They just asked for their certificates to be > included. They didn't do anything wrong. I've watched Microsoft pull > this for years...do whatever they can get away with. Include > Microsoft's proprietary and partially implemented OOXML as an open > standard? Well it came to a vote; it's not Microsoft's fault that > their distributors crashed the proceedings. > > Red Hat and others were at the working group for UEFI Secure Boot. They did not ask for a SBCA. Apparently everybody was talking about signing code and certificates in UEFI but nobody put any thinking on how to get the certificates in the mainboard. -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) _______________________________________________ This message is from the kde-promo mailing list. Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription.