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: Thu, 15 Mar 2018 10:29:41 -0700 [thread overview]
Message-ID: <1521134981.5348.62.camel@HansenPartnership.com> (raw)
In-Reply-To: <1521134074.3547.629.camel@linux.vnet.ibm.com>
On Thu, 2018-03-15 at 13:14 -0400, Mimi Zohar wrote:
> On Thu, 2018-03-15 at 10:08 -0700, James Bottomley wrote:
> >
> > On Thu, 2018-03-15 at 12:19 -0400, Mimi Zohar wrote:
>
> >
> > >
> > > If EFI is extending the TPM, will the events be added to the TPM
> > > event log or to the IMA measurement list?
> >
> > I'm not proposing any changes to the tpm_pcr_extend API. ?At the
> > moment it does an extend without logging, so that's what it will do
> > in the EFI driver case as well. ?That means logging is still the
> > responsibility of the caller.
>
> Does EFI support extending multiple TPM banks?
The specs are here:
https://trustedcomputinggroup.org/tcg-efi-protocol-specification/
As I said, I'm not planning to change the tpm_pcr_.. API. ?At the
moment for a TPM2 we extend all banks in the tpm_pcr_extend() API, so
that's what we'll continue to do ... including extending the sha256
banks with the sha1 hash, which seems to be our current practice.
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-15 17:29 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
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 [this message]
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=1521134981.5348.62.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).