From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Cc: Petr Vorel <pvorel@suse.cz>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
linux-integrity@vger.kernel.org
Subject: [PATCH v4 0/4] TPM 2.0 fixes in IMA tests
Date: Wed, 30 Sep 2020 18:02:10 +0200 [thread overview]
Message-ID: <20200930160214.29358-1-pvorel@suse.cz> (raw)
Hi Mimi, Lakshmi,
changes v3->v4:
test1:
* require 1.3.1 instead of 1.3 (simplification)
test2
* use --ignore-violations if evmctl >= 1.3.1 available
* check error only for 1.3.1, for others check only the result
* check for ima_policy=tcb (or ima_tcb) and require 1.3.1 if used
(to get --ignore-violations)
Kind regards,
Petr
Petr Vorel (4):
IMA: Move get_algorithm_digest(), set_digest_index() to ima_setup.sh
IMA: Rewrite ima_boot_aggregate.c to new API
ima_tpm.sh: Fix calculating boot aggregate
ima_tpm.sh: Fix calculating PCR aggregate
.../integrity/ima/src/ima_boot_aggregate.c | 113 ++++---
.../integrity/ima/tests/ima_measurements.sh | 62 +---
.../security/integrity/ima/tests/ima_setup.sh | 84 +++++-
.../security/integrity/ima/tests/ima_tpm.sh | 284 ++++++++++++++----
4 files changed, 371 insertions(+), 172 deletions(-)
--
2.28.0
next reply other threads:[~2020-09-30 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 16:02 Petr Vorel [this message]
2020-09-30 16:02 ` [PATCH v4 1/4] IMA: Move get_algorithm_digest(), set_digest_index() to ima_setup.sh Petr Vorel
2020-09-30 16:02 ` [PATCH v4 2/4] IMA: Rewrite ima_boot_aggregate.c to new API Petr Vorel
2020-09-30 16:02 ` [PATCH v4 3/4] ima_tpm.sh: Fix calculating boot aggregate Petr Vorel
2020-09-30 16:02 ` [PATCH v4 4/4] ima_tpm.sh: Fix calculating PCR aggregate Petr Vorel
2020-10-01 3:32 ` Mimi Zohar
2020-10-01 7:26 ` 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=20200930160214.29358-1-pvorel@suse.cz \
--to=pvorel@suse.cz \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=nramas@linux.microsoft.com \
--cc=zohar@linux.vnet.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