From: Mimi Zohar <zohar@linux.ibm.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] IMA: Verify IMA buffer passing through the kexec barrier
Date: Tue, 14 Jul 2020 21:41:49 -0400 [thread overview]
Message-ID: <1594777309.12900.237.camel@linux.ibm.com> (raw)
In-Reply-To: <20200702153545.3126-3-t-josne@linux.microsoft.com>
On Thu, 2020-07-02 at 11:35 -0400, Lachlan Sneff wrote:
> Add a testcase that verifies that kexec correctly passes
> the IMA buffer through the soft reboot.
>
> This test must be run standalone, since it runs kexec.
>
> Signed-off-by: Lachlan Sneff <t-josne@linux.microsoft.com>
Depending on the policy, the measurement list could be exactly the
same from one boot to the next. ?This test simply checks that the
first N number of measurements are the same. ?It doesn't verify that
there are additional measurements, nor does it check that there is an
additional "boot_aggregate" after the kexec. ?At minimum the test
should verify the existence of multiple "boot_aggregate" values in the
measurement list.
A more complete test would walk the measurement list, re-calculating
the PCR digests, and then compare the recalculated PCRS against the
TPM PCRs. ?If all the measurements were properly carried across the
kexec, the PCR digests should match.
Mimi
prev parent reply other threads:[~2020-07-15 1:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 15:35 [LTP] [PATCH 0/2] Test cmdline measurement and IMA buffer passing through kexec Lachlan Sneff
2020-07-02 15:35 ` [LTP] [PATCH 1/2] IMA: Verify that the kernel cmdline is passed and measured correctly through the kexec barrier Lachlan Sneff
2020-07-15 0:58 ` Mimi Zohar
2020-07-15 8:03 ` Petr Vorel
2020-07-15 19:38 ` Lachlan Sneff
2020-07-15 19:40 ` Mimi Zohar
2020-07-15 8:18 ` Petr Vorel
2020-07-15 19:46 ` Lachlan Sneff
2020-07-02 15:35 ` [LTP] [PATCH 2/2] IMA: Verify IMA buffer passing " Lachlan Sneff
2020-07-15 1:41 ` Mimi Zohar [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=1594777309.12900.237.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=ltp@lists.linux.it \
/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