NablaSquaredG

3 ms·

1.
by NablaSquaredG 5y ago
By finding a bug in the PSP. Heck, bugs like Meltdown and Spectre were found. And exploits on the PSP have already been demonstrated, see here https://github.com/PSPReverse/amd-sp-glitch
2.
by NablaSquaredG 5y ago
> BIOS flashing from the OS has been a thing for a long, long time now. Heck my XPS 13 running Linux even gets BIOS updates from apt-get. Yes, I forgot to add that point. It's also just as bad as the other options, because it means
3.
by NablaSquaredG 5y ago
As far as I know, Intel does exactly that (or at least allows vendors to do that, I think HP does that) IIRC, in Intel's case, the chipset has the vendor keys burned into it. This is not an issue, as the chipset is not a part you would
4.
by NablaSquaredG 5y ago
There are a couple of issues I see with this. First, the security argument is nonsense in my opinion. This "feature" only prevents an attacker from flashing a modified, malicious BIOS on to the server. But: If an attacker manages
5.
by NablaSquaredG 5y ago
locking: At least some AMD CPUs (EPYC, TR PRO, Ryzen Pro) can have cryptographic keys burned into the silicon by the BIOS (Dell and Lenovo do that) Once a CPU has those keys burned into it, it is locked to motherboards of this specific vend
6.
by NablaSquaredG 5y ago
This is not correct. The locks does happen on the CPU level. If the board cannot provide a BIOS with a valid signature from the key that was burned into the CPU, the CPU will refuse to boot (PSB prevents it from booting)
7.
Responsible disclosure? Never heard of that(github.com)
3 points by NablaSquaredG 7y ago|1 comments
8.
by NablaSquaredG 7y ago
Well, if it's optimised out at "-O3", I usually don't care. If you have some numerical code you can optimise further (even though you're using "-O3" or "-ffast-math"), things become interesting!