From: Ken Goldman <kgold@linux.ibm.com>
To: Mimi Zohar <zohar@linux.ibm.com>, GUO Zihua <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: Tue, 29 Aug 2023 10:09:51 -0400 [thread overview]
Message-ID: <28aefb27-8f8c-e77e-4e21-8b467738dce1@linux.ibm.com> (raw)
In-Reply-To: <90b4b5573182ec68b2da2f9ef2bc6567d724f8f1.camel@linux.ibm.com>
On 8/17/2023 10:19 AM, Mimi Zohar wrote:
> Before we can introduce this sort of change, we would need to introduce
> an IMA measurement list version. Perhaps its time to define an IMA
> security critical-data record, which would include this and other
> information. The measurement list itself would need to include a
> version number.
FYI, the TCG specified UEFI event log has a standard first record. The
events themselves do not have a version number.
That first record is itself versioned, so it can change over time.
The record has various version numbers, a count of PCR banks, a mapping
from algorithm number to algorithm size, and a sized vendor specific area.
next prev parent reply other threads:[~2023-08-29 14:11 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
2023-08-29 14:09 ` Ken Goldman [this message]
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=28aefb27-8f8c-e77e-4e21-8b467738dce1@linux.ibm.com \
--to=kgold@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=guozihua@huawei.com \
--cc=linux-integrity@vger.kernel.org \
--cc=zohar@linux.ibm.com \
/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