lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 20 Jan 2022 16:55:10 +0000 From: Sean Christopherson <seanjc@...gle.com> To: Liam Merwick <liam.merwick@...cle.com> Cc: Paolo Bonzini <pbonzini@...hat.com>, Vitaly Kuznetsov <vkuznets@...hat.com>, Wanpeng Li <wanpengli@...cent.com>, Jim Mattson <jmattson@...gle.com>, Joerg Roedel <joro@...tes.org>, kvm@...r.kernel.org, linux-kernel@...r.kernel.org, Tom Lendacky <thomas.lendacky@....com>, Brijesh Singh <brijesh.singh@....com> Subject: Re: [PATCH 3/9] KVM: SVM: Don't intercept #GP for SEV guests On Thu, Jan 20, 2022, Liam Merwick wrote: > On 20/01/2022 01:07, Sean Christopherson wrote: > > Never intercept #GP for SEV guests as reading SEV guest private memory > > will return cyphertext, i.e. emulating on #GP can't work as intended. > > > > "ciphertext" seems to be the convention. Huh, indeed it does seem to be way more common, and cipher is the proper root. Stupid English, why can't we have encrypt+cypher or encript+cipher? Thanks! I'll get these fixed.
Powered by blists - more mailing lists