From: Mimi Zohar <zohar@linux.ibm.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 2/2] IMA: Add a test to verify importing a certificate into keyring
Date: Wed, 24 Jun 2020 12:41:08 -0400 [thread overview]
Message-ID: <1593016868.27152.88.camel@linux.ibm.com> (raw)
In-Reply-To: <20200617234957.10611-3-t-josne@linux.microsoft.com>
Hi Lachlan,
On Wed, 2020-06-17 at 19:49 -0400, Lachlan Sneff wrote:
> Add an IMA measurement test that verifies that an x509 certificate
> can be imported into the .ima keyring and measured correctly.
Please expand this, explaining that the x509 certificate needs to be
signed by a key on one of the trusted keyrings.
Once there is a reliable way of adding a key to the IMA keyring, this
opens up a lot of other testing possibilities.
>
> Signed-off-by: Lachlan Sneff <t-josne@linux.microsoft.com>
> ---
> .../kernel/security/integrity/ima/README.md | 21 +++++++++
> .../security/integrity/ima/tests/ima_keys.sh | 47 ++++++++++++++++++-
> 2 files changed, 66 insertions(+), 2 deletions(-)
>
> diff --git a/testcases/kernel/security/integrity/ima/README.md b/testcases/kernel/security/integrity/ima/README.md
> index 16a1f48c3..e41f7b570 100644
> --- a/testcases/kernel/security/integrity/ima/README.md
> +++ b/testcases/kernel/security/integrity/ima/README.md
> @@ -16,6 +16,27 @@ CONFIG_INTEGRITY=y
> CONFIG_IMA=y
> ```
>
> +IMA Key Import test
> +-------------
> +
> +`ima_keys.sh` requires an x509 key to be generated and placed
> +at `/etc/keys/x509_ima.der`.
The filename "/etc/keys/x509_ima.der" is configurable. ?It's based on
CONFIG_IMA_X509_PATH Kconfig option. ?Perhaps extract it from the
running kernel's Kconfig?
> +
> +The x509 public key 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 kernel must be built
> +with one of the keys you generate.
Please reword this to convey that the public key must be built into
the kernel and loaded onto a trusted keyring (eg.
.builtin_trusted_keys, .secondary_trusted_keyring)
> +
> +As well as what's required for the IMA tests, the following are also required
> +in the kernel configuration:
> +```
> +CONFIG_IMA_READ_POLICY=y
> +CONFIG_SYSTEM_TRUSTED_KEYRING=y
> +CONFIG_SYSTEM_TRUSTED_KEYS="/etc/keys/ima-local-ca.pem"
> +```
> +
> EVM tests
> ---------
>
> diff --git a/testcases/kernel/security/integrity/ima/tests/ima_keys.sh b/testcases/kernel/security/integrity/ima/tests/ima_keys.sh
> index 2b5324dbf..1d9824aba 100755
> --- a/testcases/kernel/security/integrity/ima/tests/ima_keys.sh
> +++ b/testcases/kernel/security/integrity/ima/tests/ima_keys.sh
> @@ -5,10 +5,12 @@
> #
> # 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
>
> +CERT_FILE="${CERT_FILE:-/etc/keys/x509_ima.der}"
> +
> . ima_setup.sh
>
> # Based on https://lkml.org/lkml/2019/12/13/564.
> @@ -64,4 +66,45 @@ test1()
> tst_res TPASS "specified keyrings were measured correctly"
> }
>
> +
> +# Test that a cert can be imported into the ".ima" keyring correctly.
> +test2() {
> + local keyring_id key_id test_file=$(mktemp)
> +
> + [ -f $CERT_FILE ] || tst_brk TCONF "missing $CERT_FILE"
> +
> + if ! openssl x509 -in $CERT_FILE -inform der > /dev/null; then
> + tst_brk TCONF "The suppled cert file ($CERT_FILE) is not a valid x509 certificate"
> + fi
> +
> + tst_res TINFO "adding a cert to the .ima keyring ($CERT_FILE)"
> +
> + keyring_id=$(keyctl show %:.ima | sed -n 2p | \
> + sed 's/^[[:space:]]*//' | cut -d' ' -f1) || \
> + tst_btk TCONF "unable to retrieve .ima keyring id"
Using "keyctl describe" returns the keyring id as the first token,
making it simpler to parse.
Mimi
> +
> + if ! tst_is_num "$keyring_id"; then
> + tst_brk TCONF "unable to parse keyring id from keyring"
> + fi
> +
> + evmctl import $CERT_FILE "$keyring_id" > /dev/null || \
> + tst_brk TCONF "unable to import a cert into the .ima keyring"
> +
> + grep -F ".ima" "$ASCII_MEASUREMENTS" | tail -n1 | cut -d' ' -f6 | \
> + xxd -r -p > $test_file || \
> + tst_brk TCONF "cert not found in ascii_runtime_measurements log"
> +
> + if ! openssl x509 -in $test_file -inform der > /dev/null; then
> + tst_brk TCONF "The cert logged in ascii_runtime_measurements is not a valid x509 certificate"
> + fi
> +
> + if cmp -s "$test_file" $CERT_FILE; then
> + tst_res TPASS "logged cert matches original cert"
> + else
> + tst_res TFAIL "logged cert does not match original cert"
> + fi
> +
> + rm $test_file
> +}
> +
> tst_run
next prev parent reply other threads:[~2020-06-24 16:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 23:49 [LTP] [PATCH v3 0/2] IMA: Verify measurement of certificates Lachlan Sneff
2020-06-17 23:49 ` [LTP] [PATCH v3 1/2] IMA: Add a test to verify measurment of keys Lachlan Sneff
2020-06-18 20:28 ` Petr Vorel
2020-06-24 13:21 ` Mimi Zohar
2020-06-24 15:27 ` Mimi Zohar
2020-06-17 23:49 ` [LTP] [PATCH v3 2/2] IMA: Add a test to verify importing a certificate into keyring Lachlan Sneff
2020-06-18 20:14 ` Petr Vorel
2020-06-24 16:41 ` Mimi Zohar [this message]
2020-06-24 19:59 ` Lachlan Sneff
2020-06-24 20:02 ` Mimi Zohar
2020-07-14 12:10 ` 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=1593016868.27152.88.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--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