From: (Anonymous)
I guess I should wait for sysdev.microsoft.com to come back up, but I can't help but wonder why they wouldn't just sign certificates that the firmwares would use to in turn verify the signatures of the bootloaders. I don't know the capabilities of EFI, but these certificates could be stored anywhere, most logically on EFI system partitions (or whatever they're called). It would remove the need for the shim code, which does look like a bit of a technical kludge to me.

Did I miss something?
From:
Anonymous
OpenID
Identity URL: 
User
Account name:
Password:
If you don't have an account you can create one now.
Subject:
HTML doesn't work in the subject.

Message:

If you are unable to use this captcha for any reason, please contact us by email at support@dreamwidth.org


 
Notice: This account is set to log the IP addresses of everyone who comments.
Links will be displayed as unclickable URLs to help prevent spam.

Profile

Matthew Garrett

About Matthew

Power management, mobile and firmware developer on Linux. Security developer at Nebula. Ex-biologist. @mjg59 on Twitter. Content here should not be interpreted as the opinion of my employer.

Expand Cut Tags

No cut tags