From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it, linux-integrity@vger.kernel.org,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@huawei.com>
Subject: Re: [LTP] [RFC PATCH 2/2] security/ima: Run measurements after policy
Date: Fri, 26 Jan 2018 14:11:45 +0100 [thread overview]
Message-ID: <20180126131145.GB12731@rei> (raw)
In-Reply-To: <20180111202821.31639-3-pvorel@suse.cz>
Hi!
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> runtest/ima | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/runtest/ima b/runtest/ima
> index 20d2e0810..3462d12b1 100644
> --- a/runtest/ima
> +++ b/runtest/ima
> @@ -1,5 +1,5 @@
> #DESCRIPTION:Integrity Measurement Architecture (IMA)
> -ima01 ima_measurements.sh
> -ima02 ima_policy.sh
> +ima01 ima_policy.sh
> +ima02 ima_measurements.sh
> ima03 ima_tpm.sh
> ima04 ima_violations.sh
Uh, depending on order of testcases in runtest file is broken anyways,
what is the real problem here?
Also I suppose that we may as well rename the test ids (e.g. ima01) to
match the shell script name, since I find it more descriptive.
--
Cyril Hrubis
chrubis@suse.cz
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 2/2] security/ima: Run measurements after policy
Date: Fri, 26 Jan 2018 14:11:45 +0100 [thread overview]
Message-ID: <20180126131145.GB12731@rei> (raw)
In-Reply-To: <20180111202821.31639-3-pvorel@suse.cz>
Hi!
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> runtest/ima | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/runtest/ima b/runtest/ima
> index 20d2e0810..3462d12b1 100644
> --- a/runtest/ima
> +++ b/runtest/ima
> @@ -1,5 +1,5 @@
> #DESCRIPTION:Integrity Measurement Architecture (IMA)
> -ima01 ima_measurements.sh
> -ima02 ima_policy.sh
> +ima01 ima_policy.sh
> +ima02 ima_measurements.sh
> ima03 ima_tpm.sh
> ima04 ima_violations.sh
Uh, depending on order of testcases in runtest file is broken anyways,
what is the real problem here?
Also I suppose that we may as well rename the test ids (e.g. ima01) to
match the shell script name, since I find it more descriptive.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-01-27 10:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 20:28 [RFC PATCH 0/2] IMA: Rewrite tests into new API + fixes Petr Vorel
2018-01-11 20:28 ` [LTP] " Petr Vorel
2018-01-11 20:28 ` [RFC PATCH 1/2] security/ima: " Petr Vorel
2018-01-11 20:28 ` [LTP] " Petr Vorel
2018-01-26 13:09 ` Cyril Hrubis
2018-01-26 13:09 ` Cyril Hrubis
2018-01-11 20:28 ` [RFC PATCH 2/2] security/ima: Run measurements after policy Petr Vorel
2018-01-11 20:28 ` [LTP] " Petr Vorel
2018-01-26 13:11 ` Cyril Hrubis [this message]
2018-01-26 13:11 ` Cyril Hrubis
2018-01-26 18:03 ` Petr Vorel
2018-01-26 18:03 ` Petr Vorel
2018-01-28 0:57 ` Mimi Zohar
2018-01-28 0:57 ` Mimi Zohar
2018-01-24 17:12 ` [LTP] [RFC PATCH 0/2] IMA: Rewrite tests into new API + fixes Petr Vorel
2018-01-24 17:36 ` Mimi Zohar
2018-01-24 17:36 ` [LTP] " Mimi Zohar
2018-01-25 20:30 ` Petr Vorel
2018-01-25 20:30 ` [LTP] " Petr Vorel
2018-01-25 20:40 ` Petr Vorel
2018-01-25 20:40 ` Petr Vorel
2018-01-25 22:29 ` Mimi Zohar
2018-01-25 22:29 ` [LTP] " Mimi Zohar
2018-01-26 17:51 ` Petr Vorel
2018-01-26 17:51 ` [LTP] " Petr Vorel
2018-01-28 0:47 ` Mimi Zohar
2018-01-28 0:47 ` [LTP] " Mimi Zohar
2018-01-29 19:58 ` Mimi Zohar
2018-01-29 19:58 ` [LTP] " Mimi Zohar
2018-01-31 15:01 ` Nayna Jain
2018-01-31 15:01 ` [LTP] " Nayna Jain
2018-01-26 13:16 ` Cyril Hrubis
2018-01-26 13:16 ` Cyril Hrubis
2018-01-26 18:11 ` Petr Vorel
2018-02-06 13:19 ` 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=20180126131145.GB12731@rei \
--to=chrubis@suse.cz \
--cc=dmitry.kasatkin@huawei.com \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--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 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.