IMA: Add a test to verify importing a certificate into custom keyring
PATCH 1/1 IMA: Add a test to verify importing a certificate into custom keyring
A test for verifying importing an x509 certificate into a keyring and validating the key measurement performed by IMA is needed.
Add an IMA measurement test that verifies that an x509 certificate can be imported into a custom keyring and measured correctly.
A certificate used by the test is included in the datafiles/keys directory.
Using a custom keyring for the test is preferred over using a pre-existing/built-in keyring, such as .ima, since there may be restrictions to importing any cert into a built-in keyring. For example, the .ima keyring requires that the imported certs be signed by a kernel private key in certain kernel configurations.
---
.../kernel/security/integrity/ima/README.md | 20 +++-----
.../security/integrity/ima/datafiles/Makefile | 11 ++---
.../integrity/ima/datafiles/keys/Makefile | 31 ++++++++++++
.../integrity/ima/datafiles/keys/x509.der | Bin 0 -> 784 bytes
.../integrity/ima/datafiles/policy/Makefile | 31 ++++++++++++
.../datafiles/{ => policy}/keycheck.policy | 0
.../ima/datafiles/{ => policy}/measure.policy | 0
.../{ => policy}/measure.policy-invalid | 0
.../security/integrity/ima/tests/ima_keys.sh | 45 +++++++++++++++++-
9 files changed, 117 insertions(+), 21 deletions(-)
create mode 100644 testcases/kernel/security/integrity/ima/datafiles/keys/Makefile
create mode 100644 testcases/kernel/security/integrity/ima/datafiles/keys/x509.der
create mode 100644 testcases/kernel/security/integrity/ima/datafiles/policy/Makefile
rename testcases/kernel/security/integrity/ima/datafiles/{ => policy}/keycheck.policy (100%)
rename testcases/kernel/security/integrity/ima/datafiles/{ => policy}/measure.policy (100%)
rename testcases/kernel/security/integrity/ima/datafiles/{ => policy}/measure.policy-invalid (100%)testcases/kernel/security/integrity/ima/README.md +7 -13
@@ -16,25 +16,19 @@ space, may contain equivalent measurement tcb rules, detecting them would require `IMA_READ_POLICY=y` therefore ignore this option. ### IMA key import test -`ima_keys.sh` requires a x509 public key, by default in `/etc/keys/x509_ima.der` -(defined in `CONFIG_IMA_X509_PATH` kernel config option). -The key must be signed by the private key you generate. Follow these instructions: -https://manpages.ubuntu.com/manpages/disco/man1/evmctl.1.html#generate%20trusted%20keys -The test cannot be set-up automatically because the x509 public key must be -built into the kernel and loaded onto a trusted keyring -(e.g. `.builtin_trusted_keys`, `.secondary_trusted_keyring`). - -As well as what's required for the IMA tests, the following are also required +As well as what's required for the IMA tests, the following is also required in the kernel configuration: ``` CONFIG_IMA_READ_POLICY=y -CONFIG_IMA_X509_PATH="/etc/keys/x509_ima.der" -CONFIG_SYSTEM_TRUSTED_KEYRING=y -CONFIG_SYSTEM_TRUSTED_KEYS="/etc/keys/ima-local-ca.pem" ``` -Test also requires loaded policy with `func=KEY_CHECK`, see example in `keycheck.policy`. +You must also add the following line to /etc/ima/ima-policy and reboot. +``` +measure func=KEY_CHECK keyrings=key_import_test template=ima-buf +``` + +The test also requires loaded policy with `func=KEY_CHECK`, see example in `keycheck.policy`. ## EVM tests
testcases/kernel/security/integrity/ima/datafiles/Makefile +5 -6
@@ -1,5 +1,5 @@ # -# testcases/kernel/security/integrity/ima/policy testcases Makefile. +# kernel/security/integrity/ima testcase Makefile. # # Copyright (C) 2009, Cisco Systems Inc. #
@@ -18,14 +18,13 @@ # 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. # # Ngie Cooper, July 2009 +# Lachlan Sneff, July 2020 # top_srcdir ?= ../../../../../.. -include $(top_srcdir)/include/mk/env_pre.mk +include $(top_srcdir)/include/mk/env_pre.mk -INSTALL_DIR := testcases/data/ima_policy +SUBDIRS := policy keys -INSTALL_TARGETS := measure* - -include $(top_srcdir)/include/mk/generic_leaf_target.mk +include $(top_srcdir)/include/mk/generic_trunk_target.mk
testcases/kernel/security/integrity/ima/datafiles/keys/Makefile new file +31 -0
@@ -0,0 +1,31 @@ +# +# testcases/kernel/security/integrity/ima/policy testcases Makefile. +# +# Copyright (C) 2009, Cisco Systems Inc. +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License along +# with this program; if not, write to the Free Software Foundation, Inc., +# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. +# +# Lachlan Sneff, July 2020 +# + +top_srcdir ?= ../../../../../../.. + +include $(top_srcdir)/include/mk/env_pre.mk + +INSTALL_DIR := testcases/data/ima_keys + +INSTALL_TARGETS := x509.der + +include $(top_srcdir)/include/mk/generic_leaf_target.mk
testcases/kernel/security/integrity/ima/datafiles/keys/x509.der new file binary +0 -0
testcases/kernel/security/integrity/ima/datafiles/policy/Makefile new file +31 -0
@@ -0,0 +1,31 @@ +# +# testcases/kernel/security/integrity/ima/policy testcases Makefile. +# +# Copyright (C) 2009, Cisco Systems Inc. +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License along +# with this program; if not, write to the Free Software Foundation, Inc., +# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. +# +# Ngie Cooper, July 2009 +# + +top_srcdir ?= ../../../../../../.. + +include $(top_srcdir)/include/mk/env_pre.mk + +INSTALL_DIR := testcases/data/ima_policy + +INSTALL_TARGETS := measure* + +include $(top_srcdir)/include/mk/generic_leaf_target.mk
testcases/kernel/security/integrity/ima/datafiles/policy/keycheck.policy renamed from testcases/kernel/security/integrity/ima/datafiles/keycheck.policy +0 -0
testcases/kernel/security/integrity/ima/datafiles/policy/measure.policy renamed from testcases/kernel/security/integrity/ima/datafiles/measure.policy +0 -0
testcases/kernel/security/integrity/ima/datafiles/policy/measure.policy-invalid renamed from testcases/kernel/security/integrity/ima/datafiles/measure.policy-invalid +0 -0
testcases/kernel/security/integrity/ima/tests/ima_keys.sh +43 -2
55 lines not on this page · raw message
Signature · 1 line
2.25.1
PATCH 1/1 IMA: Add a test to verify importing a certificate into custom keyring
Gentle ping to Mimi and Petr to review.
Quoted 270 lines · Lachlan Sneff
A test for verifying importing an x509 certificate into a keyring and validating the key measurement performed by IMA is needed.
Add an IMA measurement test that verifies that an x509 certificate can be imported into a custom keyring and measured correctly.
A certificate used by the test is included in the
datafiles/keysdirectory.Using a custom keyring for the test is preferred over using a pre-existing/built-in keyring, such as
.ima, since there may be restrictions to importing any cert into a built-in keyring. For example, the.imakeyring requires that the imported certs be signed by a kernel private key in certain kernel configurations.Signed-off-by Lachlan Sneff <[email protected]>--- .../kernel/security/integrity/ima/README.md | 20 +++----- .../security/integrity/ima/datafiles/Makefile | 11 ++--- .../integrity/ima/datafiles/keys/Makefile | 31 ++++++++++++ .../integrity/ima/datafiles/keys/x509.der | Bin 0 -> 784 bytes .../integrity/ima/datafiles/policy/Makefile | 31 ++++++++++++ .../datafiles/{ => policy}/keycheck.policy | 0 .../ima/datafiles/{ => policy}/measure.policy | 0 .../{ => policy}/measure.policy-invalid | 0 .../security/integrity/ima/tests/ima_keys.sh | 45 +++++++++++++++++- 9 files changed, 117 insertions(+), 21 deletions(-)create mode 100644 testcases/kernel/security/integrity/ima/datafiles/keys/Makefile create mode 100644 testcases/kernel/security/integrity/ima/datafiles/keys/x509.der create mode 100644 testcases/kernel/security/integrity/ima/datafiles/policy/Makefile rename testcases/kernel/security/integrity/ima/datafiles/{ => policy}/keycheck.policy (100%) rename testcases/kernel/security/integrity/ima/datafiles/{ => policy}/measure.policy (100%) rename testcases/kernel/security/integrity/ima/datafiles/{ => policy}/measure.policy-invalid (100%)
testcases/kernel/security/integrity/ima/README.md +7
-13@@ -16,25 +16,19 @@ space, may contain equivalent measurement tcb rules, detecting them would require `IMA_READ_POLICY=y` therefore ignore this option. ### IMA key import test -`ima_keys.sh` requires a x509 public key, by default in `/etc/keys/x509_ima.der` -(defined in `CONFIG_IMA_X509_PATH` kernel config option). -The key must be signed by the private key you generate. Follow these instructions: -https://manpages.ubuntu.com/manpages/disco/man1/evmctl.1.html#generate%20trusted%20keys -The test cannot be set-up automatically because the x509 public key must be -built into the kernel and loaded onto a trusted keyring -(e.g. `.builtin_trusted_keys`, `.secondary_trusted_keyring`). - -As well as what's required for the IMA tests, the following are also required +As well as what's required for the IMA tests, the following is also required in the kernel configuration: ``` CONFIG_IMA_READ_POLICY=y -CONFIG_IMA_X509_PATH="/etc/keys/x509_ima.der" -CONFIG_SYSTEM_TRUSTED_KEYRING=y -CONFIG_SYSTEM_TRUSTED_KEYS="/etc/keys/ima-local-ca.pem" ``` -Test also requires loaded policy with `func=KEY_CHECK`, see example in `keycheck.policy`. +You must also add the following line to /etc/ima/ima-policy and reboot. +``` +measure func=KEY_CHECK keyrings=key_import_test template=ima-buf +``` + +The test also requires loaded policy with `func=KEY_CHECK`, see example in `keycheck.policy`. ## EVM teststestcases/kernel/security/integrity/ima/datafiles/Makefile +5
-6@@ -1,5 +1,5 @@ # -# testcases/kernel/security/integrity/ima/policy testcases Makefile. +# kernel/security/integrity/ima testcase Makefile. # # Copyright (C) 2009, Cisco Systems Inc. #@@ -18,14 +18,13 @@ # 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. # # Ngie Cooper, July 2009 +# Lachlan Sneff, July 2020 # top_srcdir ?= ../../../../../.. -include $(top_srcdir)/include/mk/env_pre.mk +include $(top_srcdir)/include/mk/env_pre.mk -INSTALL_DIR := testcases/data/ima_policy +SUBDIRS := policy keys -INSTALL_TARGETS := measure* - -include $(top_srcdir)/include/mk/generic_leaf_target.mk +include $(top_srcdir)/include/mk/generic_trunk_target.mktestcases/kernel/security/integrity/ima/datafiles/keys/Makefile new file +31
-0@@ -0,0 +1,31 @@ +# +# testcases/kernel/security/integrity/ima/policy testcases Makefile. +# +# Copyright (C) 2009, Cisco Systems Inc. +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License along +# with this program; if not, write to the Free Software Foundation, Inc., +# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. +# +# Lachlan Sneff, July 2020 +# + +top_srcdir ?= ../../../../../../.. + +include $(top_srcdir)/include/mk/env_pre.mk + +INSTALL_DIR := testcases/data/ima_keys + +INSTALL_TARGETS := x509.der + +include $(top_srcdir)/include/mk/generic_leaf_target.mktestcases/kernel/security/integrity/ima/datafiles/keys/x509.der new file binary +0
-0testcases/kernel/security/integrity/ima/datafiles/policy/Makefile new file +31
-0@@ -0,0 +1,31 @@ +# +# testcases/kernel/security/integrity/ima/policy testcases Makefile. +# +# Copyright (C) 2009, Cisco Systems Inc. +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License along +# with this program; if not, write to the Free Software Foundation, Inc., +# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. +# +# Ngie Cooper, July 2009 +# + +top_srcdir ?= ../../../../../../.. + +include $(top_srcdir)/include/mk/env_pre.mk + +INSTALL_DIR := testcases/data/ima_policy + +INSTALL_TARGETS := measure* + +include $(top_srcdir)/include/mk/generic_leaf_target.mktestcases/kernel/security/integrity/ima/datafiles/policy/keycheck.policy renamed from testcases/kernel/security/integrity/ima/datafiles/keycheck.policy +0
-0testcases/kernel/security/integrity/ima/datafiles/policy/measure.policy renamed from testcases/kernel/security/integrity/ima/datafiles/measure.policy +0
-0testcases/kernel/security/integrity/ima/datafiles/policy/measure.policy-invalid renamed from testcases/kernel/security/integrity/ima/datafiles/measure.policy-invalid +0
-0testcases/kernel/security/integrity/ima/tests/ima_keys.sh +43
-2@@ -5,8 +5,8 @@ # # Verify that keys are measured correctly based on policy. -TST_NEEDS_CMDS="grep mktemp cut sed tr" -TST_CNT=1 +TST_NEEDS_CMDS="grep mktemp cut sed tr xxd keyctl evmctl openssl cmp" +TST_CNT=2 TST_NEEDS_DEVICE=1 . ima_setup.sh@@ -65,4 +65,45 @@ test1() tst_res TPASS "specified keyrings were measured correctly" } +# Create a custom keyring and import a certficate to that +test2() { + local custom_keyring_id temp_file="file.txt" \ + cert_file="$TST_DATAROOT/x509.der" + + tst_res TINFO "checking for correct IMA policy" + + [ -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)" + + if ! grep "measure func=KEY_CHECK.*keyrings=.*key_import_test" $IMA_POLICY > /dev/null; then + tst_brk TCONF "the IMA policy does not include the key_import_test keyring. See the LTP IMA README." + fi + + tst_res TINFO "creating a custom keyring (key_import_test keyring)" + + custom_keyring_id=$(keyctl newring key_import_test @s) || \ + tst_brk TCONF "unable to create a new keyring" + + tst_is_num "$custom_keyring_id" || \ + tst_brk TCONF "unable to parse custom keyring id" + + evmctl import $cert_file "$custom_keyring_id" > /dev/null || \ + tst_brk TCONF "unable to import a cert into the key_import_test keyring" + + grep "key_import_test" "$ASCII_MEASUREMENTS" | tail -n1 | cut -d' ' -f6 | \ + xxd -r -p > $temp_file || \ + tst_brk TCONF "keyring not found in $ASCII_MEASUREMENTS" + + if ! openssl x509 -in $temp_file -inform der > /dev/null; then + tst_brk TCONF "the cert logged in $ASCII_MEASUREMENTS is not a valid x509 certificate" + fi + + if cmp -s $temp_file $cert_file; then + tst_res TPASS "logged cert matches original cert" + else + tst_res TFAIL "logged cert does not match original cert" + fi +} + tst_run
Mimi Zohar
maintainerQuoted 2 lines · Lachlan Sneff
A test for verifying importing an x509 certificate into a keyring and validating the key measurement performed by IMA is needed.
Isn't the main purpose of this patch to verify the certificate being loaded onto a keyring is properly measured. ?The rest is just details. ?Please update the Subject line accordingly.
Quoted 10 lines
Add an IMA measurement test that verifies that an x509 certificate can be imported into a custom keyring and measured correctly.
A certificate used by the test is included in the
datafiles/keysdirectory.Using a custom keyring for the test is preferred over using a pre-existing/built-in keyring, such as
.ima, since there may be restrictions to importing any cert into a built-in keyring. For example, the.imakeyring requires that the imported certs be signed by a kernel private key in certain kernel configurations.
First describe the problem, then provide the solution. ?In this case, perhaps something like:
There may be restrictions importing a certificate onto a builtin trusted keyring. ?For example ... ? For this reason, this test defines a userspace keyring.
(Please remember to limit the patch description line width to 72 chars.)
Quoted 27 lines
Signed-off-by Lachlan Sneff <[email protected]>--- .../kernel/security/integrity/ima/README.md | 20 +++----- .../security/integrity/ima/datafiles/Makefile | 11 ++--- .../integrity/ima/datafiles/keys/Makefile | 31 ++++++++++++ .../integrity/ima/datafiles/keys/x509.der | Bin 0 -> 784 bytes .../integrity/ima/datafiles/policy/Makefile | 31 ++++++++++++ .../datafiles/{ => policy}/keycheck.policy | 0 .../ima/datafiles/{ => policy}/measure.policy | 0 .../{ => policy}/measure.policy-invalid | 0 .../security/integrity/ima/tests/ima_keys.sh | 45 +++++++++++++++++- 9 files changed, 117 insertions(+), 21 deletions(-) create mode 100644 testcases/kernel/security/integrity/ima/datafiles/keys/Makefile create mode 100644 testcases/kernel/security/integrity/ima/datafiles/keys/x509.der create mode 100644 testcases/kernel/security/integrity/ima/datafiles/policy/Makefile rename testcases/kernel/security/integrity/ima/datafiles/{ => policy}/keycheck.policy (100%) rename testcases/kernel/security/integrity/ima/datafiles/{ => policy}/measure.policy (100%) rename testcases/kernel/security/integrity/ima/datafiles/{ => policy}/measure.policy-invalid (100%)testcases/kernel/security/integrity/ima/README.md +0
-0@@ -16,25 +16,19 @@ space, may contain equivalent measurement tcb rules, detecting them would require `IMA_READ_POLICY=y` therefore ignore this option. ### IMA key import test
testcases/kernel/security/integrity/ima/README.md space, may contain equivalent measurement tcb rules, detecting them would · line 28
Quoted 10 lines
testcases/kernel/security/integrity/ima/README.md +0
-9-`ima_keys.sh` requires a x509 public key, by default in `/etc/keys/x509_ima.der` -(defined in `CONFIG_IMA_X509_PATH` kernel config option). -The key must be signed by the private key you generate. Follow these instructions: -https://manpages.ubuntu.com/manpages/disco/man1/evmctl.1.html#generate%20trusted%20keys -The test cannot be set-up automatically because the x509 public key must be -built into the kernel and loaded onto a trusted keyring -(e.g. `.builtin_trusted_keys`, `.secondary_trusted_keyring`). - -As well as what's required for the IMA tests, the following are also required
This patch adds a new test, that shouldn't affect the existing test. ?If test1 changes, then it needs to be highlighted in the patch description.
testcases/kernel/security/integrity/ima/README.md space, may contain equivalent measurement tcb rules, detecting them would · line 26
Quoted 11 lines
testcases/kernel/security/integrity/ima/README.md +2
-4+As well as what's required for the IMA tests, the following is also required in the kernel configuration: ``` CONFIG_IMA_READ_POLICY=y -CONFIG_IMA_X509_PATH="/etc/keys/x509_ima.der" -CONFIG_SYSTEM_TRUSTED_KEYRING=y -CONFIG_SYSTEM_TRUSTED_KEYS="/etc/keys/ima-local-ca.pem" ``` -Test also requires loaded policy with `func=KEY_CHECK`, see example in `keycheck.policy`. +You must also add the following line to /etc/ima/ima-policy and reboot.
Documentation should be written in the third person. ?For example, instead of "you must", "A key measurement rule must be defined in the IMA policy. For example, ...."
Quoted 13 lines
testcases/kernel/security/integrity/ima/README.md +5
-0+``` +measure func=KEY_CHECK keyrings=key_import_test template=ima-buf +``` + +The test also requires loaded policy with `func=KEY_CHECK`, see example in `keycheck.policy`. ## EVM teststestcases/kernel/security/integrity/ima/datafiles/Makefile +0
-0
testcases/kernel/security/integrity/ima/datafiles/Makefile line 2
Quoted 3 lines
testcases/kernel/security/integrity/ima/datafiles/Makefile +1
-1@@ -1,5 +1,5 @@ # -# testcases/kernel/security/integrity/ima/policy testcases Makefile. +# kernel/security/integrity/ima testcase Makefile.
This change doesn't look right.
Quoted 4 lines
testcases/kernel/security/integrity/ima/datafiles/Makefile +0
-0# # Copyright (C) 2009, Cisco Systems Inc. #
testcases/kernel/security/integrity/ima/datafiles/Makefile line 26
Quoted 10 lines
testcases/kernel/security/integrity/ima/datafiles/Makefile +2
-1@@ -18,14 +18,13 @@ # 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. # # Ngie Cooper, July 2009 +# Lachlan Sneff, July 2020 # top_srcdir ?= ../../../../../.. -include $(top_srcdir)/include/mk/env_pre.mk +include $(top_srcdir)/include/mk/env_pre.mk
Please review the actual patch before posting it. ?Changes like this are unnecessary.
testcases/kernel/security/integrity/ima/datafiles/Makefile line 30
Quoted 8 lines
testcases/kernel/security/integrity/ima/datafiles/Makefile +2
-4-INSTALL_DIR := testcases/data/ima_policy +SUBDIRS := policy keys -INSTALL_TARGETS := measure* - -include $(top_srcdir)/include/mk/generic_leaf_target.mk +include $(top_srcdir)/include/mk/generic_trunk_target.mk
When making changes to someone else's code, please Cc them on the change. ?Use "git blame" to get the commit author.
testcases/kernel/security/integrity/ima/datafiles/keys/Makefile line 4
Quoted 10 lines
testcases/kernel/security/integrity/ima/datafiles/keys/Makefile new file +4
-0@@ -0,0 +1,31 @@ +# +# testcases/kernel/security/integrity/ima/policy testcases Makefile. +# +# Copyright (C) 2009, Cisco Systems Inc.
Hm, aren't you working for Microsoft? ?If you're moving existing code, please move that code separately from any other changes. ?Newer files probably use the SPDX format.
Quoted 116 lines
testcases/kernel/security/integrity/ima/datafiles/keys/Makefile new file +27
-0+# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License along +# with this program; if not, write to the Free Software Foundation, Inc., +# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. +# +# Lachlan Sneff, July 2020 +# + +top_srcdir ?= ../../../../../../.. + +include $(top_srcdir)/include/mk/env_pre.mk + +INSTALL_DIR := testcases/data/ima_keys + +INSTALL_TARGETS := x509.der + +include $(top_srcdir)/include/mk/generic_leaf_target.mktestcases/kernel/security/integrity/ima/datafiles/keys/x509.der new file binary +0
-0testcases/kernel/security/integrity/ima/datafiles/policy/Makefile new file +31
-0@@ -0,0 +1,31 @@ +# +# testcases/kernel/security/integrity/ima/policy testcases Makefile. +# +# Copyright (C) 2009, Cisco Systems Inc. +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License along +# with this program; if not, write to the Free Software Foundation, Inc., +# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. +# +# Ngie Cooper, July 2009 +# + +top_srcdir ?= ../../../../../../.. + +include $(top_srcdir)/include/mk/env_pre.mk + +INSTALL_DIR := testcases/data/ima_policy + +INSTALL_TARGETS := measure* + +include $(top_srcdir)/include/mk/generic_leaf_target.mktestcases/kernel/security/integrity/ima/datafiles/policy/keycheck.policy renamed from testcases/kernel/security/integrity/ima/datafiles/keycheck.policy +0
-0testcases/kernel/security/integrity/ima/datafiles/policy/measure.policy renamed from testcases/kernel/security/integrity/ima/datafiles/measure.policy +0
-0testcases/kernel/security/integrity/ima/datafiles/policy/measure.policy-invalid renamed from testcases/kernel/security/integrity/ima/datafiles/measure.policy-invalid +0
-0testcases/kernel/security/integrity/ima/tests/ima_keys.sh +2
-2@@ -5,8 +5,8 @@ # # Verify that keys are measured correctly based on policy. -TST_NEEDS_CMDS="grep mktemp cut sed tr" -TST_CNT=1 +TST_NEEDS_CMDS="grep mktemp cut sed tr xxd keyctl evmctl openssl cmp" +TST_CNT=2 TST_NEEDS_DEVICE=1 . ima_setup.sh
testcases/kernel/security/integrity/ima/tests/ima_keys.sh test1() · line 68
Quoted 4 lines
testcases/kernel/security/integrity/ima/tests/ima_keys.sh +1
-0@@ -65,4 +65,45 @@ test1() tst_res TPASS "specified keyrings were measured correctly" } +# Create a custom keyring and import a certficate to that
What is a custom keyring? ?Try inverting the sentence - "Import a certificate onto a newly created keyring."
testcases/kernel/security/integrity/ima/tests/ima_keys.sh test1() · line 69
Quoted 1 line
testcases/kernel/security/integrity/ima/tests/ima_keys.sh +1
-0+test2() {
The patch description should mention this patch defines an additional ima_keys.sh test. ?Another difference between test1 and test2 is that doesn't require root privileges.
Quoted 30 lines
testcases/kernel/security/integrity/ima/tests/ima_keys.sh +30
-0+ local custom_keyring_id temp_file="file.txt" \ + cert_file="$TST_DATAROOT/x509.der" + + tst_res TINFO "checking for correct IMA policy" + + [ -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)" + + if ! grep "measure func=KEY_CHECK.*keyrings=.*key_import_test" $IMA_POLICY > /dev/null; then + tst_brk TCONF "the IMA policy does not include the key_import_test keyring. See the LTP IMA README." + fi + + tst_res TINFO "creating a custom keyring (key_import_test keyring)" + + custom_keyring_id=$(keyctl newring key_import_test @s) || \ + tst_brk TCONF "unable to create a new keyring" + + tst_is_num "$custom_keyring_id" || \ + tst_brk TCONF "unable to parse custom keyring id" + + evmctl import $cert_file "$custom_keyring_id" > /dev/null || \ + tst_brk TCONF "unable to import a cert into the key_import_test keyring" + + grep "key_import_test" "$ASCII_MEASUREMENTS" | tail -n1 | cut -d' ' -f6 | \ + xxd -r -p > $temp_file || \ + tst_brk TCONF "keyring not found in $ASCII_MEASUREMENTS" + + if ! openssl x509 -in $temp_file -inform der > /dev/null; then + tst_brk TCONF "the cert logged in $ASCII_MEASUREMENTS is not a valid x509 certificate"
testcases/kernel/security/integrity/ima/tests/ima_keys.sh test1() · line 109
Quoted 10 lines
testcases/kernel/security/integrity/ima/tests/ima_keys.sh +9
-0+ fi + + if cmp -s $temp_file $cert_file; then + tst_res TPASS "logged cert matches original cert" + else + tst_res TFAIL "logged cert does not match original cert" + fi +} + tst_run
Normally when code is duplicated with only minor changes, it implies that the code can be refactored.
Mimi
Hi Lachlan,
Quoted 2 lines
A test for verifying importing an x509 certificate into a keyring and validating the key measurement performed by IMA is needed.
I suppose you're going to send new version of this patch (rebased + fix according to Mimi's comments).
IMHO that should be your last not yet merged patch.
FYI: I'm planning to fix ima_tpm.sh and then implement autoloading IMA policy (when possible).
Kind regards,
Petr
On 7/31/20 1:02 AM, Petr Vorel wrote:
Hi Petr,
Quoted 11 lines
Quoted 2 lines
A test for verifying importing an x509 certificate into a keyring and validating the key measurement performed by IMA is needed.
I suppose you're going to send new version of this patch (rebased + fix according to Mimi's comments).
IMHO that should be your last not yet merged patch.
FYI: I'm planning to fix
ima_tpm.shand then implement autoloading IMA policy (when possible).
Yes - Lachlan will send the new version of the patch set (rebased to your latest changes and also addressing Mimi's comments).
thanks,
-lakshmi