From: zohar@linux.vnet.ibm.com (Mimi Zohar)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] security: Fix IMA Kconfig for dependencies on ARM64
Date: Mon, 12 Mar 2018 19:19:42 -0400 [thread overview]
Message-ID: <1520896782.3547.245.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180312230501.GJ24717@ziepe.ca>
On Mon, 2018-03-12 at 17:05 -0600, Jason Gunthorpe wrote:
> On Mon, Mar 12, 2018 at 06:58:45PM -0400, Mimi Zohar wrote:
> > On Mon, 2018-03-12 at 15:59 -0600, Jason Gunthorpe wrote:
> > > On Mon, Mar 12, 2018 at 05:53:18PM -0400, Mimi Zohar wrote:
> > >
> > > > Using Kconfig to force the TPM to be builtin is not required, but
> > > > helpful. ?Users interested in IMA-measurement could configure the TPM
> > > > as builtin themselves. ?Without the TPM builtin, IMA goes into TPM-
> > > > bypass mode.
> > >
> > > This issues, broadly speaking, we have lots of TPM drivers, selecting
> > > only some to actually support IMA shows we have some kind of problem
> > > here.
> >
> > True, IMA is not selecting the older TPM vendor specific modules, but
> > only the newer TPM_TIS and now TPM_CRB modules. ?That doesn't imply
> > that IMA only supports some TPMs. ?It means that by default, these
> > TPMs are builtin. ?Anyone building a kernel, can select the vendor
> > specific TPM to be builtin.
>
> That doesn't help distros, which is the main point of the complaint
> with this scheme :)
Years ago because of faulty TPM drivers, IMA was disabled in one of
the main distro's. ?Deciding which vendor specific TPMs should be
builtin, is a discussion between the distro's and TPM vendors.
Mimi
--
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-12 23:19 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
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 [this message]
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=1520896782.3547.245.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.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).