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=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_2 autolearn=no 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 B4BC4C3A5AA for ; Wed, 4 Sep 2019 20:27:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9696D21726 for ; Wed, 4 Sep 2019 20:27:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727900AbfIDU1B (ORCPT ); Wed, 4 Sep 2019 16:27:01 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:24694 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729278AbfIDU1B (ORCPT ); Wed, 4 Sep 2019 16:27:01 -0400 Received: from pps.filterd (m0098410.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x84KHLJ9028697 for ; Wed, 4 Sep 2019 16:27:00 -0400 Received: from e06smtp02.uk.ibm.com (e06smtp02.uk.ibm.com [195.75.94.98]) by mx0a-001b2d01.pphosted.com with ESMTP id 2utkte91sc-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 04 Sep 2019 16:26:59 -0400 Received: from localhost by e06smtp02.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 4 Sep 2019 21:26:57 +0100 Received: from b06cxnps4076.portsmouth.uk.ibm.com (9.149.109.198) by e06smtp02.uk.ibm.com (192.168.101.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Wed, 4 Sep 2019 21:26:53 +0100 Received: from b06wcsmtp001.portsmouth.uk.ibm.com (b06wcsmtp001.portsmouth.uk.ibm.com [9.149.105.160]) by b06cxnps4076.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x84KQrua49807588 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 4 Sep 2019 20:26:53 GMT Received: from b06wcsmtp001.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id F1D12A405C; Wed, 4 Sep 2019 20:26:52 +0000 (GMT) Received: from b06wcsmtp001.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 29F3CA4054; Wed, 4 Sep 2019 20:26:52 +0000 (GMT) Received: from dhcp-9-31-103-196.watson.ibm.com (unknown [9.31.103.196]) by b06wcsmtp001.portsmouth.uk.ibm.com (Postfix) with ESMTP; Wed, 4 Sep 2019 20:26:52 +0000 (GMT) Subject: Re: TPM 2.0 Linux sysfs interface From: Mimi Zohar To: Jason Gunthorpe Cc: Jordan Hand , Tadeusz Struk , Piotr =?ISO-8859-1?Q?Kr=F3l?= , linux-integrity@vger.kernel.org, Alexey Dobriyan Date: Wed, 04 Sep 2019 16:26:51 -0400 In-Reply-To: <20190904194348.GA3757@ziepe.ca> References: <20190828161502.GC933@ziepe.ca> <20190902192632.GB5393@ziepe.ca> <1567460118.10024.316.camel@linux.ibm.com> <20190903055523.GA4500@ziepe.ca> <1567553383.4937.29.camel@linux.ibm.com> <20190904055829.GA3936@ziepe.ca> <1567596658.4937.40.camel@linux.ibm.com> <20190904194348.GA3757@ziepe.ca> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 (3.20.5-1.fc24) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 x-cbid: 19090420-0008-0000-0000-000003111F9B X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19090420-0009-0000-0000-00004A2F767D Message-Id: <1567628811.4937.57.camel@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-09-04_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=3 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1909040203 Sender: linux-integrity-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-integrity@vger.kernel.org On Wed, 2019-09-04 at 16:43 -0300, Jason Gunthorpe wrote: > On Wed, Sep 04, 2019 at 07:30:58AM -0400, Mimi Zohar wrote: > > On Wed, 2019-09-04 at 02:58 -0300, Jason Gunthorpe wrote: > > > On Tue, Sep 03, 2019 at 07:29:43PM -0400, Mimi Zohar wrote: > > > > > > > This discussion is going around in circles.  There are enough people > > > > asking that the kernel provide at least the TPM version (eg. TPM 1.2 > > > > or TPM 2.0).  Userspace applications/regression tests shouldn't have > > > > to figure out the TPM version by sending a TPM command and seeing if > > > > it fails.  That really isn't asking a lot. > > > > > > A single version number could be appropriate for sysfs > > > > > > > I would also prefer not having to be dependent on a userspace > > > > application to read the TPM PCRs in order to verify the IMA > > > > measurement list. > > > > > > Why? > > > > Being dependent on a userspace application implies a level of trust, > > that might not be warranted, depending on the system's > > configuration. > > Surely if you can trust 'cat' you can trust something that does ioctl? Ok, you've agreed with the kernel exporting the TPM information.  How it is exported remains to be defined. Mimi