From: Mimi Zohar <zohar@linux.ibm.com>
To: Vitaly Chikunov <vt@altlinux.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH v4] ima-evm-utils: Add some tests for evmctl
Date: Wed, 31 Jul 2019 10:04:05 -0400 [thread overview]
Message-ID: <1564581845.4189.184.camel@linux.ibm.com> (raw)
In-Reply-To: <20190731052658.12785-1-vt@altlinux.org>
Hi Vitaly,
On Wed, 2019-07-31 at 08:26 +0300, Vitaly Chikunov wrote:
> Run `make check' to execute the tests.
> Currently only ima_hash, (evm) sign, (evm) verify, ima_sign, and
> ima_verify are tested.
>
> Signed-off-by: Vitaly Chikunov <vt@altlinux.org>
I probably haven't applied all of the prereq patches, so some of the
tests are failing. As a result, I found:
- (Thank you for changing the simple "FOR" variable.) There are a
couple of "ADD_FOR_TEXT" instead of "ADD_TEXT_FOR".
> +
> +# Test if xattr $attr in $file matches $pref'ix
> +# Show error and fail otherwise.
> +_test_xattr() {
> + local file=$1 attr=$2 pref=$3
> + local test_for=${ADD_TEXT_FOR:+ for $ADD_TEXT_FOR}
> +
> + if ! getfattr -n $attr -e hex $file | egrep -qx "$attr=$pref"; then
> + red_if_failure
> + echo "Did not find expected hash$text_for:"
^test_for
> + echo " $attr=$pref"
> + echo ""
> + echo "Actual output below:"
> + getfattr -n $attr -e hex $file | sed 's/^/ /'
> + color_restore
> + rm $file
> + ADD_TEXT_FOR=
> + return $FAIL
> + fi
> + ADD_TEXT_FOR=
> +}
Mimi
prev parent reply other threads:[~2019-07-31 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 5:26 [PATCH v4] ima-evm-utils: Add some tests for evmctl Vitaly Chikunov
2019-07-31 14:04 ` Mimi Zohar [this message]
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=1564581845.4189.184.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=vt@altlinux.org \
--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;
as well as URLs for NNTP newsgroup(s).