From: Mimi Zohar <zohar@linux.ibm.com>
To: Petr Vorel <pvorel@suse.cz>,
Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it, linuxtestproject.agent@gmail.com
Subject: Re: [LTP] ima_tpm.sh: properly detect failure to verify the IMA measurement list
Date: Thu, 27 Aug 2026 09:38:38 -0400 [thread overview]
Message-ID: <24ebd275e8d93d5557c709322e312f5a2b02d95d.camel@linux.ibm.com> (raw)
In-Reply-To: <20260827102252.GA442795@pevik>
Hi Andrea, Petr,
Thank you for reviewing/testing/updating the v1/v2.
On Thu, 2026-08-27 at 12:22 +0200, Petr Vorel wrote:
> > @Petr can you please take a look?
>
> Sure :). FYI I already did have a brief look yesterday, and I also triggered CI
> jobs for v1 and wait them to finish. Of course I'll rerun them for v2.
>
> @Mimi FYI v1 patch triggers failure - it just calculate a different
> aggregate PCR-10. Although the commit subject is "properly detect failure" ..
> I'm not sure if this is a false negative or the current code on master just did
> not find error (false positive). As I said, I'll rerun v2 and let you know if
> it's the same.
I've been testing on real HW with a physical TPM, not in a virtual VM.
Without a dont_measure policy rule to eliminate the "systemd_unit_file_t"
measurements, the number of measurements grows really fast. The results of
test2 looks like:
ima_tpm 2 TINFO: verify PCR values
ima_tpm 2 TINFO: real PCR-10:
'ea84103155e8a91974c2706db94f91e396dad3f91430648224e19f17790716d8'
ima_tpm 2 TINFO: ignoring 5 violations
ima_tpm 2 TINFO: aggregate PCR-10:
'4608820a46bb8ad5e4d95b6f94273e76f1f12ca8c61b84d01aaed7b0fb226a74'
ima_tpm 2 TPASS: aggregate PCR value matched real PCR value (line: 7147/7634)
>
> Testing on openSUSE Tumbleweed x86_64 VM with kernel: 7.1.8-1, virtualized TPM
> 2.0, evmctl 1.6.2. Working master [1], broken with your patch [2].
Interesting that with this simple patch, test2 now fails.
Mimi
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-27 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 22:29 [LTP] [PATCH v2] ima_tpm.sh: properly detect failure to verify the IMA measurement list Mimi Zohar
2026-08-26 22:29 ` Mimi Zohar
2026-08-27 3:05 ` [LTP] " linuxtestproject.agent
2026-08-27 6:56 ` Andrea Cervesato via ltp
2026-08-27 10:22 ` Petr Vorel
2026-08-27 12:59 ` Petr Vorel
2026-08-27 13:38 ` Mimi Zohar [this message]
2026-09-10 19:41 ` [LTP] [PATCH v2] " Petr Vorel
2026-09-10 19:41 ` Petr Vorel
-- strict thread matches above, loose matches on Subject: below --
2026-08-26 0:34 [LTP] [PATCH] " Mimi Zohar
2026-08-26 1:15 ` [LTP] " linuxtestproject.agent
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=24ebd275e8d93d5557c709322e312f5a2b02d95d.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=andrea.cervesato@suse.com \
--cc=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.