> Specifically, a malicious hypervisor can selectively drop any writes of an AMD SEV-ES and SEV-SNP guest that occurred at an attacker-chosen point
This strikes me as the thing that Raymond Chen calls "being on the other side of this airtight hatchway" [0]. That is, if you've already got control of the Hypervisor then ... you can do anything you want to the guest operating systems. Right?
This strikes me as the thing that Raymond Chen calls "being on the other side of this airtight hatchway" [0]. That is, if you've already got control of the Hypervisor then ... you can do anything you want to the guest operating systems. Right?
0: https://devblogs.microsoft.com/oldnewthing/20060508-22/?p=31...