TheHolm to [email protected]English • 3 months agoAMD won't patch all chips affected by severe data theft vulnerability — Ryzen 3000, 2000, and 1000 will not get patched for 'Sinkclose'www.tomshardware.comexternal-linkmessage-square183fedilinkarrow-up1536arrow-down124file-textcross-posted to: selfhostedpcmasterraceamdhardware
arrow-up1512arrow-down1external-linkAMD won't patch all chips affected by severe data theft vulnerability — Ryzen 3000, 2000, and 1000 will not get patched for 'Sinkclose'www.tomshardware.comTheHolm to [email protected]English • 3 months agomessage-square183fedilinkfile-textcross-posted to: selfhostedpcmasterraceamdhardware
Here we are - 3600 which was still under manufacture 2-3 years ago are not get patched. Shame on you AMD, if it is true.
minus-square0^2linkfedilinkEnglish5•3 months agoWait yeah can someone explain why this exploit couldn’t be used to say rewrite it to support coreboot and turn this into a good thing?
minus-square@[email protected]linkfedilinkEnglish1•edit-23 months agobecause you need the coreboot people to write firmware that can initialise the system, and that probably takes a lot of reverse engineering I don’t know much about this, but I assume there’s little to no effort for corebooting on the amd side, I’ve only seen intel platforms with coreboot
minus-square@[email protected]linkfedilinkEnglish0•3 months agoThere are coreboot AMD projects for the framework laptop
Wait yeah can someone explain why this exploit couldn’t be used to say rewrite it to support coreboot and turn this into a good thing?
because you need the coreboot people to write firmware that can initialise the system, and that probably takes a lot of reverse engineering
I don’t know much about this, but I assume there’s little to no effort for corebooting on the amd side, I’ve only seen intel platforms with coreboot
There are coreboot AMD projects for the framework laptop