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 3/4] IMA/ima_keys.sh: Fix policy readability check Date: Tue, 28 Jul 2020 00:30:40 +0200 [thread overview] Message-ID: <20200727223041.13110-4-pvorel@suse.cz> (raw) In-Reply-To: <20200727223041.13110-1-pvorel@suse.cz> Using a proper check with cat, because file attributes were fixed in ffb122de9a60 ("ima: Reflect correct permissions for policy") in v4.18. Fixes: d2768c84e ("IMA: Add a test to verify measurement of keys") Signed-off-by: Petr Vorel <pvorel@suse.cz> --- Changes v4->v5: * use require_ima_policy_content * moved helper function to previous commit .../kernel/security/integrity/ima/tests/ima_keys.sh | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/testcases/kernel/security/integrity/ima/tests/ima_keys.sh b/testcases/kernel/security/integrity/ima/tests/ima_keys.sh index 2f6c2b027..5a77deec1 100755 --- a/testcases/kernel/security/integrity/ima/tests/ima_keys.sh +++ b/testcases/kernel/security/integrity/ima/tests/ima_keys.sh @@ -19,15 +19,7 @@ test1() tst_res TINFO "verifying key measurement for keyrings and templates specified in IMA policy file" - [ -f $IMA_POLICY ] || tst_brk TCONF "missing $IMA_POLICY" - - [ -r $IMA_POLICY ] || tst_brk TCONF "cannot read IMA policy (CONFIG_IMA_READ_POLICY=y required)" - - keycheck_lines=$(grep "func=KEY_CHECK" $IMA_POLICY) - if [ -z "$keycheck_lines" ]; then - tst_brk TCONF "ima policy does not specify \"func=KEY_CHECK\"" - fi - + keycheck_lines=$(require_ima_policy_content "func=KEY_CHECK" "") keycheck_line=$(echo "$keycheck_lines" | grep "keyrings" | head -n1) if [ -z "$keycheck_line" ]; then -- 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 3/4] IMA/ima_keys.sh: Fix policy readability check Date: Tue, 28 Jul 2020 00:30:40 +0200 [thread overview] Message-ID: <20200727223041.13110-4-pvorel@suse.cz> (raw) In-Reply-To: <20200727223041.13110-1-pvorel@suse.cz> Using a proper check with cat, because file attributes were fixed in ffb122de9a60 ("ima: Reflect correct permissions for policy") in v4.18. Fixes: d2768c84e ("IMA: Add a test to verify measurement of keys") Signed-off-by: Petr Vorel <pvorel@suse.cz> --- Changes v4->v5: * use require_ima_policy_content * moved helper function to previous commit .../kernel/security/integrity/ima/tests/ima_keys.sh | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/testcases/kernel/security/integrity/ima/tests/ima_keys.sh b/testcases/kernel/security/integrity/ima/tests/ima_keys.sh index 2f6c2b027..5a77deec1 100755 --- a/testcases/kernel/security/integrity/ima/tests/ima_keys.sh +++ b/testcases/kernel/security/integrity/ima/tests/ima_keys.sh @@ -19,15 +19,7 @@ test1() tst_res TINFO "verifying key measurement for keyrings and templates specified in IMA policy file" - [ -f $IMA_POLICY ] || tst_brk TCONF "missing $IMA_POLICY" - - [ -r $IMA_POLICY ] || tst_brk TCONF "cannot read IMA policy (CONFIG_IMA_READ_POLICY=y required)" - - keycheck_lines=$(grep "func=KEY_CHECK" $IMA_POLICY) - if [ -z "$keycheck_lines" ]; then - tst_brk TCONF "ima policy does not specify \"func=KEY_CHECK\"" - fi - + keycheck_lines=$(require_ima_policy_content "func=KEY_CHECK" "") keycheck_line=$(echo "$keycheck_lines" | grep "keyrings" | head -n1) if [ -z "$keycheck_line" ]; then -- 2.27.0
next prev parent 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 [PATCH v5 0/4] IMA: kexec cmdline measurement Petr Vorel 2020-07-27 22:30 ` [LTP] " 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 ` Petr Vorel [this message] 2020-07-27 22:30 ` [LTP] [PATCH v5 3/4] IMA/ima_keys.sh: Fix policy readability check 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-4-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.