From: James.Bottomley@HansenPartnership.com (James Bottomley)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] security: Fix IMA Kconfig for dependencies on ARM64
Date: Wed, 07 Mar 2018 11:08:39 -0800 [thread overview]
Message-ID: <1520449719.5558.28.camel@HansenPartnership.com> (raw)
In-Reply-To: <1520448953.10396.565.camel@linux.vnet.ibm.com>
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 <anjiandi@codeaurora.org>
> > > ?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.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-03-07 19:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 5:26 [PATCH] security: Fix IMA Kconfig for dependencies on ARM64 Jiandi An
2018-03-07 18:51 ` Jason Gunthorpe
2018-03-07 18:55 ` Mimi Zohar
2018-03-07 19:08 ` James Bottomley [this message]
2018-03-07 19:21 ` Mimi Zohar
2018-03-07 19:41 ` James Bottomley
2018-03-07 21:12 ` Jiandi An
2018-03-07 21:16 ` James Bottomley
2018-03-07 22:19 ` Mimi Zohar
2018-03-08 18:42 ` Jiandi An
2018-03-08 20:06 ` Mimi Zohar
2018-03-09 17:11 ` James Bottomley
2018-03-12 21:53 ` Mimi Zohar
2018-03-12 21:59 ` Jason Gunthorpe
2018-03-12 22:58 ` Mimi Zohar
2018-03-12 23:05 ` Jason Gunthorpe
2018-03-12 23:19 ` Mimi Zohar
2018-03-12 22:30 ` James Bottomley
2018-03-12 23:30 ` Mimi Zohar
2018-03-13 0:06 ` James Bottomley
2018-03-13 12:57 ` Safford, David (GE Global Research, US)
2018-03-14 14:41 ` James Bottomley
2018-03-14 17:08 ` Mimi Zohar
2018-03-14 17:25 ` James Bottomley
2018-03-15 16:19 ` Mimi Zohar
2018-03-15 17:08 ` James Bottomley
2018-03-15 17:14 ` Mimi Zohar
2018-03-15 17:29 ` James Bottomley
2018-03-16 16:51 ` Mimi Zohar
2018-03-11 22:06 ` Mimi Zohar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1520449719.5558.28.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).