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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 17 May 2024 17:58:01 +0200
From: Juergen Gross <jgross@...e.com>
To: Dave Hansen <dave.hansen@...el.com>,
 "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org, linux-coco@...ts.linux.dev,
 Dave Hansen <dave.hansen@...ux.intel.com>,
 Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
 Borislav Petkov <bp@...en8.de>, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] x86/kvm/tdx: Save %rbp in TDX_MODULE_CALL

On 17.05.24 17:52, Dave Hansen wrote:
> On 5/17/24 08:48, Juergen Gross wrote:
>> Is the BIOS version printed at boot enough to see what I have?
>>
>> [    0.000000] DMI: Intel Corporation D50DNP/D50DNP, BIOS
>> SE5C7411.86B.9535.D04.2312270518 12/27/2023
> 
> I honestly don't know.
> 
> What we actually need is the TDX module version. I'm not sure how
> tightly tied the TDX module is to the BIOS version. I suspect that
> they're actually completely independent.
> 
> Once we have the specific TDX module version, we can go ask the folks
> who write it if there were any RBP clobbering bugs.
> 

Okay, how to get the TDX module version?


Juergen

Download attachment "OpenPGP_0xB0DE9DD628BF132F.asc" of type "application/pgp-keys" (3684 bytes)

Download attachment "OpenPGP_signature.asc" of type "application/pgp-signature" (496 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ