From: Vitaly Chikunov <vt@altlinux.org>
To: Petr Vorel <pvorel@suse.cz>, "Bruno E. O. Meneguele" <bmeneg@redhat.com>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
linux-integrity@vger.kernel.org
Subject: Re: [RFC PATCH] ima-evm-utils: Add some tests for evmctl
Date: Sun, 28 Jul 2019 07:53:02 +0300 [thread overview]
Message-ID: <20190728045302.cziuajr3532r3b53@altlinux.org> (raw)
In-Reply-To: <20190726130708.GA4542@dell5510>
Petr, Bruno,
Thanks for reviews! I think I will rework the tests one more time. So
that they can support EVM signatures too w/o too much code duplication.
Thanks,
prev parent reply other threads:[~2019-07-28 4:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 6:18 [RFC PATCH] ima-evm-utils: Add some tests for evmctl Vitaly Chikunov
2019-07-25 14:46 ` Mimi Zohar
2019-07-25 15:38 ` Vitaly Chikunov
2019-07-26 1:03 ` Mimi Zohar
2019-07-25 21:58 ` Bruno E. O. Meneguele
2019-07-25 22:31 ` Vitaly Chikunov
2019-07-26 13:07 ` Petr Vorel
2019-07-28 4:53 ` Vitaly Chikunov [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=20190728045302.cziuajr3532r3b53@altlinux.org \
--to=vt@altlinux.org \
--cc=bmeneg@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=pvorel@suse.cz \
--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).