Profile
Matthew Garrett
About Matthew
Active Entries
- 1: Secure Boot isn't the only problem facing Linux on Windows 8 hardware
- 2: Dealing with UEFI non-volatile memory quirks
- 3: More in the series of bizarre UEFI bugs
- 4: TVs are all awful
- 5: Samsung laptop bug is not Linux specific
- 6: Playing with Thunderbolt under Linux on Apple hardware
- 7: A short introduction to TPMs
- 8: Rebooting
- 9: Update on leaked UEFI signing keys - probably no significant risk
- 10: Leaked UEFI signing keys
Expand Cut Tags
No cut tags
Re: Would you mind doing a post on what you did to get a signed shim.
Date: 2012-12-01 07:33 am (UTC)- Go to sysdev.microsoft.com and log in with a Live account.
- Follow the link to the Verisign (now Symantec) page for creating a new company account. Ignore the use of the word company - you can do this as an individual.
- Follow the instructions and purchase an individual key for code signing. You'll be emailed a form to attach a copy of your notarised ID to, so get that filled in and signed and send them back a copy by email.
- Export the key from your browser as a .p12 file.
- Go back to sysdev.microsoft.com and download the zip file containing winsign.exe. Use pesign or sbsign and the key you exported to sign this file, and then upload it to sysdev.microsoft.com to enable your account.
- Sign the legal agreements - this just involves you typing your name into a box.
- Put the file you want to get signed into a cab file. lcab will do this,
- Sign the cab file with your Verisign key. osslsigncode will do this.
- Upload the file to sysdev.microsoft.com. The uploader is Silverlight for no obviously good reason.
- Wait for the upload to be processed. I think this happens a couple of times a week, so be prepared to wait a few days (I had to)
- You'll get an email when signing is complete. Download the cab file and use cabextract to retrieve your signed binary.
Total cost is $99 plus however much it costs to get something notarised where you are.