Received: by 10.223.185.116 with SMTP id b49csp5417879wrg; Wed, 7 Mar 2018 11:22:54 -0800 (PST) X-Google-Smtp-Source: AG47ELuuNK//tqJk2retrgwjgvySlkiV1KBjAlE1xFBSGv4Lt8lkpeQR4jA9+MiGLiBuz5enCotj X-Received: by 10.99.120.199 with SMTP id t190mr18565873pgc.72.1520450574456; Wed, 07 Mar 2018 11:22:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520450574; cv=none; d=google.com; s=arc-20160816; b=ncEFvKJpLKXJOd1g0b3Fbvwi+a5NpQ+J+Q83KO8H+ErWNJb9qbEkVucEeOo5uWcu3X 3kcghHM+pFAzAQzD73Aoz9KHFDsMdsmt8KiXmBoFCnx79jqIKatzu/83NHVG3w01Q6S2 rEDKbqlnTuXvlySppylWeHGViOUyoL7YJbnTTc7is9AcOqsuDkKaSdkLg1hKZhkoHSUE STaVS6fefLyHJaRfAHOKYkDsuKxOzl0jfa/PdfoD2LgXRQsyiJm6SrEmdMbYZSgjFCbs JxeobMyXo8f84VO6RrYtqzGw5yxc05xTD5pK9x3GdBKGKLQbvxsAOE72KhfR/u/Je582 u2Jg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :mime-version:references:in-reply-to:date:cc:to:from:subject :arc-authentication-results; bh=Rfyd0vIklTIt//aiL9L8dbWCJqmvNsM6jri5+CnuMB0=; b=ZbI9pyOmMfBWntk+aGlKqNJ1pHKlzpYbMji3HYeX5UqIruyxCaDEIxFDLI9IyUcOR+ HErNDkrqWvbYadUiG3dkHAqTRylfElxRDYml3lpA/CLLfCnNipYsF0kxwHX9w1dju1vD GFlKRyhK/f7siWVnVZ2zRN+r6vNSr/OBXwGrhEQ6LJAcCbV2GouvUFCVYQWSk8T6fbfv F5fbvdrSVitXouljg9Tm0bqkkod2K6o2kg+nyqjGohoww663LfXVjHlPYPD4Wv1E8U/Q mLdxiEUIfvZyFMD+MWpD8uvQVzZbGZbrvE/qlM3g6qMic3fr2YR+GJ+0Cch1A/bROMx/ StFg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o6-v6si13311316plh.287.2018.03.07.11.22.39; Wed, 07 Mar 2018 11:22:54 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754579AbeCGTVs (ORCPT + 99 others); Wed, 7 Mar 2018 14:21:48 -0500 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:37222 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754039AbeCGTVq (ORCPT ); Wed, 7 Mar 2018 14:21:46 -0500 Received: from pps.filterd (m0098413.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w27JJtJJ129923 for ; Wed, 7 Mar 2018 14:21:45 -0500 Received: from e06smtp12.uk.ibm.com (e06smtp12.uk.ibm.com [195.75.94.108]) by mx0b-001b2d01.pphosted.com with ESMTP id 2gjhk8ms0k-1 (version=TLSv1.2 cipher=AES256-SHA256 bits=256 verify=NOT) for ; Wed, 07 Mar 2018 14:21:45 -0500 Received: from localhost by e06smtp12.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 7 Mar 2018 19:21:42 -0000 Received: from b06cxnps3074.portsmouth.uk.ibm.com (9.149.109.194) by e06smtp12.uk.ibm.com (192.168.101.142) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Wed, 7 Mar 2018 19:21:37 -0000 Received: from d06av21.portsmouth.uk.ibm.com (d06av21.portsmouth.uk.ibm.com [9.149.105.232]) by b06cxnps3074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w27JLbp766126036; Wed, 7 Mar 2018 19:21:37 GMT Received: from d06av21.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id ED9EA5203F; Wed, 7 Mar 2018 18:13:14 +0000 (GMT) Received: from localhost.localdomain (unknown [9.80.81.183]) by d06av21.portsmouth.uk.ibm.com (Postfix) with ESMTP id 87A4552045; Wed, 7 Mar 2018 18:13:13 +0000 (GMT) Subject: Re: [PATCH] security: Fix IMA Kconfig for dependencies on ARM64 From: Mimi Zohar To: James Bottomley , Jason Gunthorpe , Jiandi An Cc: dmitry.kasatkin@gmail.com, jmorris@namei.org, serge@hallyn.com, linux-integrity@vger.kernel.org, linux-ima-devel@lists.sourceforge.net, linux-ima-user@lists.sourceforge.net, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org Date: Wed, 07 Mar 2018 14:21:35 -0500 In-Reply-To: <1520449719.5558.28.camel@HansenPartnership.com> References: <1520400386-17674-1-git-send-email-anjiandi@codeaurora.org> <20180307185132.GA30102@ziepe.ca> <1520448953.10396.565.camel@linux.vnet.ibm.com> <1520449719.5558.28.camel@HansenPartnership.com> 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: 18030719-0008-0000-0000-000004D90B7B X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18030719-0009-0000-0000-00001E6C2844 Message-Id: <1520450495.10396.587.camel@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-03-07_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1803070220 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2018-03-07 at 11:08 -0800, James Bottomley wrote: > On Wed, 2018-03-07 at 13:55 -0500, Mimi Zohar wrote: > > On Wed, 2018-03-07 at 11:51 -0700, Jason Gunthorpe wrote: > > > > > > On Tue, Mar 06, 2018 at 11:26:26PM -0600, Jiandi An wrote: > > > > > > > > TPM_CRB driver is the TPM support for ARM64.  If it > > > > is built as module, TPM chip is registered after IMA > > > > init.  tpm_pcr_read() in IMA driver would fail and > > > > display the following message even though eventually > > > > there is TPM chip on the system: > > > > > > > > ima: No TPM chip found, activating TPM-bypass! (rc=-19) > > > > > > > > Fix IMA Kconfig to select TPM_CRB so TPM_CRB driver is > > > > built in kernel and initializes before IMA driver. > > > > > > > > Signed-off-by: Jiandi An > > > >  security/integrity/ima/Kconfig | 1 + > > > >  1 file changed, 1 insertion(+) > > > > > > > > diff --git a/security/integrity/ima/Kconfig > > > > b/security/integrity/ima/Kconfig > > > > index 35ef693..6a8f677 100644 > > > > +++ b/security/integrity/ima/Kconfig > > > > @@ -10,6 +10,7 @@ config IMA > > > >   select CRYPTO_HASH_INFO > > > >   select TCG_TPM if HAS_IOMEM && !UML > > > >   select TCG_TIS if TCG_TPM && X86 > > Well, this explains why IMA doesn't work on one of my X86 systems: it's > got a non i2c infineon TPM. > > > > > + select TCG_CRB if TCG_TPM && ACPI > > > >   select TCG_IBMVTPM if TCG_TPM && PPC_PSERIES > > > >   help > > > >     The Trusted Computing Group(TCG) runtime Integrity > > > > > > This seems really weird, why are any specific TPM drivers linked to > > > IMA config, we have lots of drivers.. > > > > > > I don't think I've ever seen this pattern in Kconfig before? > > > > As you've seen by the current discussions, the TPM driver needs to be > > initialized prior to IMA.  Otherwise IMA goes into TPM-bypass mode. > >  That implies that the TPM must be builtin to the kernel, and not as > > a kernel module. > > Actually, that's not necessarily true:  If we don't begin appraisal > until after the initrd phase, then the initrd can load TPM modules > before IMA starts. > > This would involve a bit of code rejigging to not require a TPM until > IMA wants to write its first measurement, but it looks doable and would > get us out of having to second guess TPM selections. The question is about measurement, not appraisal.  Although the initramfs might be measured, the initramfs can access files on the real root filesystem.  Those files need to be measured, before they are used/accessed. Mimi