From: Ken Goldman <kgold@linux.ibm.com>
To: Mimi Zohar <zohar@linux.ibm.com>,
"Jorge Ramirez-Ortiz, Foundries" <jorge@foundries.io>
Cc: dmitry.kasatkin@gmail.com, jmorris@namei.org, serge@hallyn.com,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, Jarkko Sakkinen <jarkko@kernel.org>
Subject: Re: ima - wait for tpm load
Date: Mon, 28 Jun 2021 18:04:19 -0400 [thread overview]
Message-ID: <1341c53c-1aa7-62dc-db9f-b58dcb8b7906@linux.ibm.com> (raw)
In-Reply-To: <f0c6ab70093eb9e360232482ce415e9863a8699c.camel@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
On 6/10/2021 4:31 PM, Mimi Zohar wrote:
> As I recall "extend" works pretty much from the beginning. There's no
> need to wait for the self test to complete. Registering the TPM early
> might be enough without having to wait. Or maybe check the selftest
> result.
TPM 2.0 depends somewhat on the type of self test - there are several
options. They will in some sense block other commands that use
the angorithm.
The TPM is permitted to do an extend before the hash algorithm is
tested (just not return a result) but I don't think it's required.
So:
- self test
- extend
may permit the extend to proceed while the self test is
happening, but it may not.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4490 bytes --]
prev parent reply other threads:[~2021-06-28 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 7:16 ima - wait for tpm load Jorge Ramirez-Ortiz, Foundries
2021-06-10 14:19 ` Mimi Zohar
2021-06-10 15:18 ` Jorge Ramirez-Ortiz, Foundries
2021-06-10 20:31 ` Mimi Zohar
2021-06-28 22:04 ` Ken Goldman [this message]
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=1341c53c-1aa7-62dc-db9f-b58dcb8b7906@linux.ibm.com \
--to=kgold@linux.ibm.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=jorge@foundries.io \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--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;
as well as URLs for NNTP newsgroup(s).