A month or so ago. Cfir Cohen, a member of the Google Cloud security team, alerted AMD about a problem with the Secure Encrypted Virtualization (SEV) functionality of the Epyc processors. This vulnera... AMD addresses SEV security vulnerability in Epyc CPUs with firmware update
What begins? You need to begin a round of updating Epyc servers' firmwares? I guess nobody would be looking forward to such a task, huh.
What I am trying to say is that I just don't feel comfortable when majorities for a specific idea are formed, and invariably all dissent is assumed to need quashing. It's just no fun because then the primary purpose of ideas is lost.
Aside from already being patched, the good news is this is really only an issue for VMs, and from what I can tell, shouldn't really have any impact on performance. I don't think even you understood what you said there...
Saying it like that felt more appropriate than explaining nepotism. You're still correct, though. I find having to put thoughts in to specific, expected words can at times remove meaning and effect.
Nothing serious nor performance impacts, the fix simply discard some NIST keys on VM initialization... https://www.theregister.co.uk/2019/06/26/amd_epyc_key_security_flaw/
Despite i like the image, it doesn't began at all, every CPU (or any computer part) have fail, bug, security issue. (yes even an apple or a Ryzen ). it's not new, so patching/update is a good thing, it mean that they are working on it.
Security IS serious, and VM is widely used with this kind of CPU. This is a good point for AMD to work on the pro side of their CPU
It is so serious that it depends only how the Linux VM guest is set regarding the user rights. And the fix is easy, they simply discard the ECC values the user may be able to send The only real bother is this. The fix is regenerate the PDH keys.
