From: Petr Vorel <pvorel@suse.cz> To: ltp@lists.linux.it Cc: Petr Vorel <pvorel@suse.cz>, Lachlan Sneff <t-josne@linux.microsoft.com>, Lakshmi Ramasubramanian <nramas@linux.microsoft.com>, Mimi Zohar <zohar@linux.vnet.ibm.com>, balajib@linux.microsoft.com, linux-integrity@vger.kernel.org Subject: [PATCH v5 0/4] IMA: kexec cmdline measurement Date: Tue, 28 Jul 2020 00:30:37 +0200 [thread overview] Message-ID: <20200727223041.13110-1-pvorel@suse.cz> (raw) Hi all, sending hopefully the last version. In the end I did quite few changes, thus sending patchset instead of merging without review. Tested on various setup: ima_kexec 1 TCONF: IMA policy does not specify '^measure.*func=KEXEC_CMDLINE' --- ima_kexec 1 TPASS: kexec -s -l /boot/vmlinuz-5.3.13-1-default --append=foo passed as expected ima_kexec 1 TPASS: kexec cmdline for --append=foo was measured correctly ima_kexec 2 TPASS: kexec -s -l /boot/vmlinuz-5.3.13-1-default --command-line=bar passed as expected ima_kexec 2 TPASS: kexec cmdline for --command-line=bar was measured correctly --- ima_kexec 1 TBROK: kexec failed: kexec_file_load failed: Required key not available --- ima_kexec 1 TWARN: policy not readable, it might not contain required measure func=KEXEC_CMDLINE ima_kexec 1 TBROK: unable to find a correct entry for --reuse-cmdline Kind regards, Petr Lachlan Sneff (1): IMA: Add test for kexec cmdline measurement Petr Vorel (3): IMA: Rename helper to require_ima_policy_cmdline IMA: Add policy related helpers IMA/ima_keys.sh: Fix policy readability check runtest/ima | 1 + .../kernel/security/integrity/ima/README.md | 8 ++ .../integrity/ima/datafiles/kexec.policy | 1 + .../integrity/ima/tests/evm_overlay.sh | 2 +- .../security/integrity/ima/tests/ima_kexec.sh | 111 ++++++++++++++++++ .../security/integrity/ima/tests/ima_keys.sh | 10 +- .../integrity/ima/tests/ima_measurements.sh | 2 +- .../security/integrity/ima/tests/ima_setup.sh | 41 ++++++- 8 files changed, 164 insertions(+), 12 deletions(-) create mode 100644 testcases/kernel/security/integrity/ima/datafiles/kexec.policy create mode 100755 testcases/kernel/security/integrity/ima/tests/ima_kexec.sh -- 2.27.0
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz> To: ltp@lists.linux.it Subject: [LTP] [PATCH v5 0/4] IMA: kexec cmdline measurement Date: Tue, 28 Jul 2020 00:30:37 +0200 [thread overview] Message-ID: <20200727223041.13110-1-pvorel@suse.cz> (raw) Hi all, sending hopefully the last version. In the end I did quite few changes, thus sending patchset instead of merging without review. Tested on various setup: ima_kexec 1 TCONF: IMA policy does not specify '^measure.*func=KEXEC_CMDLINE' --- ima_kexec 1 TPASS: kexec -s -l /boot/vmlinuz-5.3.13-1-default --append=foo passed as expected ima_kexec 1 TPASS: kexec cmdline for --append=foo was measured correctly ima_kexec 2 TPASS: kexec -s -l /boot/vmlinuz-5.3.13-1-default --command-line=bar passed as expected ima_kexec 2 TPASS: kexec cmdline for --command-line=bar was measured correctly --- ima_kexec 1 TBROK: kexec failed: kexec_file_load failed: Required key not available --- ima_kexec 1 TWARN: policy not readable, it might not contain required measure func=KEXEC_CMDLINE ima_kexec 1 TBROK: unable to find a correct entry for --reuse-cmdline Kind regards, Petr Lachlan Sneff (1): IMA: Add test for kexec cmdline measurement Petr Vorel (3): IMA: Rename helper to require_ima_policy_cmdline IMA: Add policy related helpers IMA/ima_keys.sh: Fix policy readability check runtest/ima | 1 + .../kernel/security/integrity/ima/README.md | 8 ++ .../integrity/ima/datafiles/kexec.policy | 1 + .../integrity/ima/tests/evm_overlay.sh | 2 +- .../security/integrity/ima/tests/ima_kexec.sh | 111 ++++++++++++++++++ .../security/integrity/ima/tests/ima_keys.sh | 10 +- .../integrity/ima/tests/ima_measurements.sh | 2 +- .../security/integrity/ima/tests/ima_setup.sh | 41 ++++++- 8 files changed, 164 insertions(+), 12 deletions(-) create mode 100644 testcases/kernel/security/integrity/ima/datafiles/kexec.policy create mode 100755 testcases/kernel/security/integrity/ima/tests/ima_kexec.sh -- 2.27.0
next reply other threads:[~2020-07-27 22:30 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-27 22:30 Petr Vorel [this message] 2020-07-27 22:30 ` [LTP] [PATCH v5 0/4] IMA: kexec cmdline measurement Petr Vorel 2020-07-27 22:30 ` [PATCH v5 1/4] IMA: Rename helper to require_ima_policy_cmdline Petr Vorel 2020-07-27 22:30 ` [LTP] " Petr Vorel 2020-07-27 22:30 ` [PATCH v5 2/4] IMA: Add policy related helpers Petr Vorel 2020-07-27 22:30 ` [LTP] " Petr Vorel 2020-07-30 19:50 ` Mimi Zohar 2020-07-30 19:50 ` [LTP] " Mimi Zohar 2020-07-31 5:26 ` Petr Vorel 2020-07-31 5:26 ` [LTP] " Petr Vorel 2020-07-27 22:30 ` [PATCH v5 3/4] IMA/ima_keys.sh: Fix policy readability check Petr Vorel 2020-07-27 22:30 ` [LTP] " Petr Vorel 2020-07-27 22:30 ` [PATCH v5 4/4] IMA: Add test for kexec cmdline measurement Petr Vorel 2020-07-27 22:30 ` [LTP] " Petr Vorel 2020-07-27 22:42 ` Lachlan Sneff 2020-07-27 22:42 ` [LTP] " Lachlan Sneff 2020-07-27 23:13 ` Petr Vorel 2020-07-27 23:13 ` [LTP] " Petr Vorel 2020-07-30 20:03 ` [PATCH v5 0/4] IMA: " Mimi Zohar 2020-07-30 20:03 ` [LTP] " Mimi Zohar
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=20200727223041.13110-1-pvorel@suse.cz \ --to=pvorel@suse.cz \ --cc=balajib@linux.microsoft.com \ --cc=linux-integrity@vger.kernel.org \ --cc=ltp@lists.linux.it \ --cc=nramas@linux.microsoft.com \ --cc=t-josne@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: linkBe 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.