Live data from Hacker News

MSI firmware signing keys leaked

github.com

1–10 of 37 posts

Re: MSI firmware signing keys leaked

#5
post #3

I would love to learn more about that. How would someone use those keys? What's beneficial, what could be useful possible cases for me? And Are my workstations in my company at risk?

If I recall correctly, at boot time CPUs retrieve the firmware along with a cryptographic signature that verifies the firmware came from the signer. Some boards choose to burn this signature into the hardware using e-fuses. If the signing key is leaked, that means someone can flash custom firmware into the chip and the CPU would be none the wiser, all while operating at Ring 0.

Re: MSI firmware signing keys leaked

#9

Does this mean that we can now custom firmwares (e.g. coreboot) on those MSI boards?

It's really fucked up that we can't disable secure boot on boards we've bought, and we have to hope their security is compromised instead. What would be the issue with requiring a very manual process to add my own CA to the board so I can load up whatever I want?

Ah, vendor lockin, got it.

Re: MSI firmware signing keys leaked

#10
post #3

I would love to learn more about that. How would someone use those keys? What's beneficial, what could be useful possible cases for me? And Are my workstations in my company at risk?

If I recall correctly, at boot time CPUs retrieve the firmware along with a cryptographic signature that verifies the firmware came from the signer. Some boards choose to burn this signature into the hardware using e-fuses. If the signing key is leaked, that means someone can flash custom firmware into the chip and the CPU would be none the wiser, all while operating at Ring 0.

CPU firmware (microcode) is signed by Intel, so it would not be affected by this leak, only motherboard firmware.
Post reply on HN