linux-kernel - Re: [PATCH v9 0/6] Add TDX Guest Attestation support

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]

Message-ID: <bb006b7a-525a-3f1b-0fc4-1620bb5bd3ba@intel.com>
Date:   Wed, 24 Aug 2022 10:12:21 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     Kuppuswamy Sathyanarayanan 
        <sathyanarayanan.kuppuswamy@...ux.intel.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org
Cc:     "H . Peter Anvin" <hpa@...or.com>,
        "Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>,
        Tony Luck <tony.luck@...el.com>,
        Andi Kleen <ak@...ux.intel.com>,
        Kai Huang <kai.huang@...el.com>,
        Wander Lairson Costa <wander@...hat.com>,
        Isaku Yamahata <isaku.yamahata@...il.com>,
        marcelo.cerri@...onical.com, tim.gardner@...onical.com,
        khalid.elmously@...onical.com, philip.cox@...onical.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v9 0/6] Add TDX Guest Attestation support

On 7/27/22 20:44, Kuppuswamy Sathyanarayanan wrote:
> An Intel SGX Quoting Enclave (QE), written specifically to support
> quoting Intel TDX TDs, uses EVERIFYREPORT2, to help check the integrity
> of the TDG.MR.REPORT. If it passes, the QE can use a certified quote
> signing key to sign a quote containing the guest TD’s measurements and
> the additional data being quoted.

(maintainer hat firmly in place, not speaking as an Intel person here...)

Let's say Intel tires of SGX and zaps it from server CPUs just like it
did clients.  Or, that Intel decides that TDX is really cool and wants
it on SGX-free clients in addition to servers.

Can the guest ABI which is introduced here work for a future attestation
architecture that does not involve SGX?