From: Mimi Zohar <zohar@linux.ibm.com>
To: "Guozihua (Scott)" <guozihua@huawei.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-integrity@vger.kernel.org
Subject: Re: [RFC PATCH -next] ima: Make tpm hash configurable
Date: Wed, 30 Aug 2023 08:27:17 -0400 [thread overview]
Message-ID: <7dc816ddc48e50de32debafbeee9c83b728aec75.camel@linux.ibm.com> (raw)
In-Reply-To: <47e478d8-1559-a3cc-94c1-a05fd79b2f0b@huawei.com>
On Wed, 2023-08-30 at 17:14 +0800, Guozihua (Scott) wrote:
> On 2023/8/19 7:17, Mimi Zohar wrote:
> > On Fri, 2023-08-18 at 09:25 +0800, Guozihua (Scott) wrote:
> >> On 2023/8/17 22:19, Mimi Zohar wrote:
> >>> On Thu, 2023-08-17 at 14:13 +0800, GUO Zihua wrote:
> > [...]
> >
> >>> Other proposals have changed the hard coded hash algorithm and PCR
> >>> value from SHA1 to SHA256. Both that proposal and this will break
> >>> existing userspace applications.
> >>
> >> This is the part I would like to "RFC" on, and thanks for the comment!
> >
> > Another proposal included all of the enabled TPM bank digests.
> Will this introduce some performance issue? I don't think we should be
> calculating various hashes on the same thing again and again.
Per TPM bank specific hashes are already being calculated and extended
into the TPM banks. Refer to ima_calc_field_array_hash().
--
thanks,
Mimi
next prev parent reply other threads:[~2023-08-30 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 6:13 [RFC PATCH -next] ima: Make tpm hash configurable GUO Zihua
2023-08-17 14:19 ` Mimi Zohar
2023-08-18 1:25 ` Guozihua (Scott)
2023-08-18 23:17 ` Mimi Zohar
2023-08-19 8:43 ` Guozihua (Scott)
2023-08-28 21:05 ` Ken Goldman
2023-08-30 9:32 ` Guozihua (Scott)
2023-08-30 19:26 ` Ken Goldman
2023-08-30 9:14 ` Guozihua (Scott)
2023-08-30 12:27 ` Mimi Zohar [this message]
2023-08-29 14:09 ` Ken Goldman
2023-08-28 20:35 ` Ken Goldman
2023-08-30 9:38 ` Guozihua (Scott)
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=7dc816ddc48e50de32debafbeee9c83b728aec75.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=guozihua@huawei.com \
--cc=linux-integrity@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