From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [LTP v4 4/5] IMA: Add a test to verify measurement of certificate imported into a keyring
Date: Mon, 31 Aug 2020 12:29:34 +0200 [thread overview]
Message-ID: <20200831102934.GB17121@dell5510> (raw)
In-Reply-To: <889c90c2777e2683749ab6d339e25aa85b192407.camel@linux.ibm.com>
Hi Mimi,
> On Fri, 2020-08-28 at 14:49 +0200, Petr Vorel wrote:
> > > On Fri, 2020-08-28 at 08:05 +0200, Petr Vorel wrote:
> > > > BTW there are also plans for reboot support [1] [2], that could be used as
> > > > workaround for configuration without CONFIG_IMA_READ_POLICY=y and
> > > > CONFIG_IMA_WRITE_POLICY=y.
> > > The reboot support could also be used for carrying the IMA measurement
> > > list across kexec and verifying the TPM PCRs.
> > Adding into my TODO list. I'd just run whole test ima_kexec.sh twice and reboot
> > in between.
> The ima_kexec.sh tests measures the kexec boot cmdline and kernel
> image. What's needed is walking the measurement list re-calculating
> the PCRs and then verifying them against the actual TPM PCRs. Maybe
> running the ima_tpm.sh test twice.
Right, thanks for clarification :).
It takes some time till reboot implementation in LTP API is implemented. But I
hope to send fix for TPM 2.0 and sha256 hash (these changes in v5.8) for
ima_tpm.sh this week.
Kind regards,
Petr
next prev parent reply other threads:[~2020-08-31 10:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 9:08 [LTP] [LTP v4 0/5] IMA: verify measurement of certificate imported into a keyring Petr Vorel
2020-08-20 9:08 ` [LTP] [LTP v4 1/5] IMA/ima_keys.sh: Fix policy content check usage Petr Vorel
2020-08-24 17:19 ` Petr Vorel
2020-08-24 17:24 ` Lakshmi Ramasubramanian
2020-08-20 9:08 ` [LTP] [LTP v4 2/5] IMA/ima_keys.sh: Require template=ima-buf, fix grep pattern Petr Vorel
2020-08-20 9:08 ` [LTP] [LTP v4 3/5] IMA: Refactor datafiles directory Petr Vorel
2020-08-28 13:18 ` Petr Vorel
2020-08-28 13:28 ` Petr Vorel
2020-08-28 16:32 ` Mimi Zohar
2020-08-31 7:39 ` Petr Vorel
2020-08-30 16:31 ` Petr Vorel
2020-08-20 9:08 ` [LTP] [LTP v4 4/5] IMA: Add a test to verify measurement of certificate imported into a keyring Petr Vorel
2020-08-26 22:15 ` Mimi Zohar
2020-08-27 13:23 ` Petr Vorel
2020-08-27 13:55 ` Petr Vorel
2020-08-27 21:34 ` Mimi Zohar
2020-08-27 22:54 ` Petr Vorel
2020-08-27 23:37 ` Mimi Zohar
2020-08-28 6:05 ` Petr Vorel
2020-08-28 11:00 ` Mimi Zohar
2020-08-28 12:40 ` Petr Vorel
2020-08-28 11:19 ` Mimi Zohar
2020-08-28 12:49 ` Petr Vorel
2020-08-28 15:21 ` Mimi Zohar
2020-08-31 10:29 ` Petr Vorel [this message]
2020-08-28 10:59 ` Mimi Zohar
2020-08-20 9:08 ` [LTP] [LTP v4 5/5] IMA/ima_keys.sh: Enhance policy checks Petr Vorel
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=20200831102934.GB17121@dell5510 \
--to=pvorel@suse.cz \
--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