From: Nayna <nayna@linux.vnet.ibm.com>
To: Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity <linux-integrity@vger.kernel.org>
Cc: ltp@lists.linux.it, Petr Vorel <pvorel@suse.cz>
Subject: Re: [PATCH] ima: skip verifying TPM 2.0 PCR values
Date: Fri, 17 May 2019 09:50:45 -0400 [thread overview]
Message-ID: <fccc3abd-f3ce-fdb1-55d7-c18ce116446c@linux.vnet.ibm.com> (raw)
In-Reply-To: <1558041162.3971.2.camel@linux.ibm.com>
On 05/16/2019 05:12 PM, Mimi Zohar wrote:
> TPM 1.2 exported the PCRs. Reading the TPM 2.0 PCRs requires a
> userspace application. For now, skip this test.
>
> Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
> ---
> testcases/kernel/security/integrity/ima/tests/ima_tpm.sh | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/testcases/kernel/security/integrity/ima/tests/ima_tpm.sh b/testcases/kernel/security/integrity/ima/tests/ima_tpm.sh
> index 0ffc3c02247d..ebe4b4c360e4 100755
> --- a/testcases/kernel/security/integrity/ima/tests/ima_tpm.sh
> +++ b/testcases/kernel/security/integrity/ima/tests/ima_tpm.sh
> @@ -88,6 +88,14 @@ test2()
> tst_res TINFO "verify PCR values"
> tst_check_cmds evmctl
>
> + local tpm_description="/sys/class/tpm/tpm0/device/description"
I do not see a "description" file on either my PowerPC or x86 systems
with TPM 2.0. Perhaps instead of testing for the "description" file, if
the "pcrs" file is not found, emit a more verbose informational message,
for eg. - "pcrs file is not found - either you are running a TPM 2.0, or
having sysfs failed to show pcrs for TPM 1.2"
Thanks & Regards,
- Nayna
next prev parent reply other threads:[~2019-05-17 13:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 21:12 [PATCH] ima: skip verifying TPM 2.0 PCR values Mimi Zohar
2019-05-17 6:51 ` Petr Vorel
2019-05-17 11:19 ` Mimi Zohar
2019-05-17 11:28 ` Petr Vorel
2019-05-17 13:50 ` Nayna [this message]
2019-05-17 15:04 ` Petr Vorel
2019-10-24 12:18 ` [LTP] " Petr Vorel
2019-10-24 17:20 ` Jarkko Sakkinen
2019-10-24 18:20 ` Jason Gunthorpe
2019-10-24 19:14 ` Jarkko Sakkinen
2019-10-24 23:36 ` Jason Gunthorpe
2019-10-28 20:51 ` Jarkko Sakkinen
2019-10-24 21:38 ` Jerry Snitselaar
2019-10-24 23:26 ` Jason Gunthorpe
2019-10-25 0:47 ` Mimi Zohar
2019-10-25 2:11 ` Jerry Snitselaar
2019-10-25 8:56 ` Petr Vorel
2019-10-25 12:52 ` Serge E. Hallyn
2019-10-25 13:22 ` Mimi Zohar
2019-10-25 13:25 ` Petr Vorel
2019-10-25 14:13 ` Jerry Snitselaar
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=fccc3abd-f3ce-fdb1-55d7-c18ce116446c@linux.vnet.ibm.com \
--to=nayna@linux.vnet.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--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).