AMI-Bios Sourcecode and UEFI Signing Key leaked?

Re:AMI-Bios Sourcecode and UEFI Signing Key leaked? by cnvogel on Friday April 05, 2013 @03:12PM (#5500403)

Yes, but you'd expect the key (Keys/FW/.priKey) to be accompanied by some useful metadata (naming the entity the key belongs to, and a certificate from microsoft validating the key) to be added to the firmware image, wouldn't you? And if there's only certificates containing "DO NOT USE" text?

But certainly, I have no idea about all that. If someone could post commands how to verify (or at least dump) connection between DER encoded RSA keys and the PK/KEK/db/dbx files (which seem to have a 40byte header, then, again DER data)... that could shed some additional light on these matters.

[ Parent | on HN ]

Re:AMI-Bios Sourcecode and UEFI Signing Key leaked? by mjg59 on Friday April 05, 2013 @03:35PM (#5500531)

There'd be no reason to expect the firmware signing key to have any relation to any of the certificates used in Secure Boot. They're used for separate purposes.

[ Parent | on HN ]

Re:AMI-Bios Sourcecode and UEFI Signing Key leaked? by marshray on Friday April 05, 2013 @03:37PM (#5500546)

You may have to remove the === BEGIN/END blah === header and run the result through 'base64 -d' first.

     openssl asn1parse (-text or -dump I forget) -inform (pem or der) -in [filename]

The private key should list 'P', 'Q', and the 'modulus'. If the modulus is the same as in the public key, it's the same.

[ Parent | on HN ]