Re: The Achilles Heel Of Secure Boot: Certificate Revocation

Nuno Silva <[email protected]> writes:
> And even without Microsoft, this appeared in an area that's not
> exactly known for compliance and perfect implementation. Secure Boot
> and UEFI, this time we will get PC firmware right, pinky promise!
>
> And considering Microsoft, don't forget it'd not be the first time
> they intentionally tried to break compatibility at the firmware level
> to put other systems at a disadvantage:

(U)EFI was neither designed nor implemented by Microsoft. It originated
in Intel, and today is managed by an industry body with dozens of
members. There are multiple implementations, although I think most are
derived from the open source one. Adoption started with hardware
vendors: Microsoft’s platform requirements followed the market rather
than leading it.  The idea that UEFI was some kind of Microsoft
compatibility-breaking conspiracy is not well supported by the history.
The reality is BIOS needed to be replaced, and the entire computer
industry understood this.

-- 
https://www.greenend.org.uk/rjk/