From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 43018C001DE for ; Fri, 28 Jul 2023 19:40:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234584AbjG1Tkq (ORCPT ); Fri, 28 Jul 2023 15:40:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52604 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233941AbjG1Tkg (ORCPT ); Fri, 28 Jul 2023 15:40:36 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A8CEE422C; Fri, 28 Jul 2023 12:40:32 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 2368B621DF; Fri, 28 Jul 2023 19:40:32 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 453DBC433C9; Fri, 28 Jul 2023 19:40:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1690573231; bh=qJSSXg7Vv8HfsIe6IzeuukyvrA8LHNwx15c3kihE4MY=; h=Date:Cc:Subject:From:To:References:In-Reply-To:From; b=u02bMwQYkSQgP5ED1FN0HqlsYwUM4SznWO+fxaXJvlcV7S5o+37OM8TrjoODwoxn2 /2cSmEOn7JTnOSKFb7iBplxH6p+ZVAXJrp63KXeO4A67sr7XBP/ckvW4Gi8PsJrZ7i NNU0RH7/DrS9tq3aT27rNYkzYkPjojU9+iau3j+ASB/LgkcbG/2FCzSBt3CS1QIAYW YGXUkgOYqzbsKltBsbO3rPGuWZRb7dZ2cGdieLUoa1xnIWmnkA+sFARiropO2fooaN 0H5bVmOw9ribjWF/PXMlV89rkzIe8iLrPZxyQ9yexIG9i+87ddJH7fwdnne642pk5c XS1eDId1tA63w== Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Fri, 28 Jul 2023 19:40:27 +0000 Message-Id: Cc: "Kuppuswamy Sathyanarayanan" , "Kuppuswamy Sathyanarayanan" , "Dionna Amalie Glaze" , "Greg Kroah-Hartman" , "Samuel Ortiz" , , , , , Subject: Re: [PATCH 1/4] keys: Introduce tsm keys From: "Jarkko Sakkinen" To: "Dan Williams" , X-Mailer: aerc 0.14.0 References: <169057265210.180586.7950140104251236598.stgit@dwillia2-xfh.jf.intel.com> <169057265801.180586.10867293237672839356.stgit@dwillia2-xfh.jf.intel.com> In-Reply-To: <169057265801.180586.10867293237672839356.stgit@dwillia2-xfh.jf.intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri Jul 28, 2023 at 7:30 PM UTC, Dan Williams wrote: > One of the common operations of a TSM (Trusted Security Module) is to > provide a way for a TVM (confidential computing guest execution > environment) to take a measurement of its run state and use that with a > key-exchange protocol to establish a shared secret with a third-party / > remote attestation agent. The concept is common across TSMs, but the This is obfuscated "white paper" alike language. I have no idea what TSM's and TVM's are and I do not want to know. Even confidential computing is useless buzzword in the context of providing a key type for attestation. I would replace "tsm" with "attestation". BR, Jarkko