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 X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9E252C43381 for ; Mon, 25 Feb 2019 23:09:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6C33421841 for ; Mon, 25 Feb 2019 23:09:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=hansenpartnership.com header.i=@hansenpartnership.com header.b="T2+QjkdS" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728941AbfBYXJe (ORCPT ); Mon, 25 Feb 2019 18:09:34 -0500 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:57652 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727421AbfBYXJe (ORCPT ); Mon, 25 Feb 2019 18:09:34 -0500 Received: from localhost (localhost [127.0.0.1]) by bedivere.hansenpartnership.com (Postfix) with ESMTP id 275B48EE1A0; Mon, 25 Feb 2019 15:09:34 -0800 (PST) Received: from bedivere.hansenpartnership.com ([127.0.0.1]) by localhost (bedivere.hansenpartnership.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y-BtaP8gFE27; Mon, 25 Feb 2019 15:09:33 -0800 (PST) Received: from [153.66.254.194] (unknown [50.35.68.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bedivere.hansenpartnership.com (Postfix) with ESMTPSA id 10DAD8EE101; Mon, 25 Feb 2019 15:09:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hansenpartnership.com; s=20151216; t=1551136173; bh=43lWbOYzSYa+tZJHqx6Z800Y8pcjZ/MTDQuOkWe7+XI=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=T2+QjkdSdYzJ4VVIJCXAg1Gj4HWTFlqFGdEvHJLtzlufTJnKNYeSxXe0pBiFdQ7L5 y1yQHbcbxCpZPR+yBzP1u7uLkAMgbIjoKUo3HpaL4NmWGwZLMDAJAn8wzgpuzZWusp Ez3EDepigreJXqSkLm4RCWVFowqbsiDUuUtSft2U= Message-ID: <1551136170.3226.95.camel@HansenPartnership.com> Subject: Re: [PATCH] tpm: Add driver for TPM over virtio From: James Bottomley To: Matthew Garrett Cc: David Tolnay , Peter Huewe , Jarkko Sakkinen , Jason Gunthorpe , linux-integrity , "Michael S. Tsirkin" , Jason Wang , virtualization@lists.linux-foundation.org, dgreid@chromium.org, apronin@chromium.org Date: Mon, 25 Feb 2019 15:09:30 -0800 In-Reply-To: References: <388c5b80-21a7-1e91-a11f-3a1c1432368b@gmail.com> <1550849416.2787.5.camel@HansenPartnership.com> <1550873900.2787.25.camel@HansenPartnership.com> <1550885645.3577.31.camel@HansenPartnership.com> <1551025819.3106.25.camel@HansenPartnership.com> <1551108969.3226.26.camel@HansenPartnership.com> <1551126043.3226.45.camel@HansenPartnership.com> <1551132882.3226.67.camel@HansenPartnership.com> <1551133927.3226.81.camel@HansenPartnership.com> <1551135106.3226.91.camel@HansenPartnership.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.6 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-integrity-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-integrity@vger.kernel.org On Mon, 2019-02-25 at 15:02 -0800, Matthew Garrett wrote: > On Mon, Feb 25, 2019 at 2:51 PM James Bottomley > wrote: > > On Mon, 2019-02-25 at 14:43 -0800, Matthew Garrett wrote: > > > You still need a transport mechanism through the hypervisor to > > > communicate with the host - what would you be using in that case > > > instead of virtio? > > > > Socsim is net transported; it's sort of the TPM equivalent of NFS > > or iSCSI storage for guests. > > Oh, so it relies on the guest being able to reach the host via > network? Hmm. That's a different security tradeoff. It presumably > also prevents any in-kernel use before networking is up? Exactly, that's why I'm not recommending it. However, the initrdless early net nastiness path has already been trodden by the NFS/iSCSI root people ... James