From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH v3 02/10] security/ima: Change order of tests
Date: Fri, 27 Apr 2018 02:03:27 +0200 [thread overview]
Message-ID: <20180427000327.GA25413@x230> (raw)
In-Reply-To: <1524759610.3647.13.camel@linux.vnet.ibm.com>
Hi Mimi,
> On Thu, 2018-04-26 at 10:32 -0400, Mimi Zohar wrote:
> > On Tue, 2018-04-24 at 20:09 +0200, Petr Vorel wrote:
> [...]
> > The original tests assumed a builtin IMA-measurement policy. Either
> > the boot command line "ima_tcb" or "ima_policy=tcb" options should
> > work. When checking the "ima_policy" for "tcb", it could be specified
> > anywhere in the list of builtin policies (eg.
> > ima_policy=appraise_tcb|secure_boot|ima).
> oops, ima_policy=appraise_tcb|secure_boot|tcb.
Thanks for clarification. I'll grep /proc/cmdline it in ima_setup.sh and TCONF if it's not met (I suppose this requirement/assumption is for all 4 tests).
> Mimi
Kind regards,
Petr
next prev parent reply other threads:[~2018-04-27 0:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 19:54 [LTP] [RFC PATCH v3 00/10] Rewrite tests into new API + fixes Petr Vorel
2018-04-19 19:54 ` [LTP] [RFC PATCH v3 01/10] security/ima: " Petr Vorel
2018-04-27 14:13 ` Mimi Zohar
2018-04-28 15:09 ` Petr Vorel
2018-04-19 19:54 ` [LTP] [RFC PATCH v3 02/10] security/ima: Change order of tests Petr Vorel
2018-04-24 18:09 ` Petr Vorel
2018-04-26 14:32 ` Mimi Zohar
2018-04-26 16:20 ` Mimi Zohar
2018-04-27 0:03 ` Petr Vorel [this message]
2018-04-19 19:54 ` [LTP] [RFC PATCH v3 03/10] ima/ima_policy.sh: Improve check of policy writability Petr Vorel
2018-04-19 19:54 ` [LTP] [RFC PATCH v3 04/10] ima/ima_policy.sh: Load whole policy with cat Petr Vorel
2018-04-19 19:54 ` [LTP] [RFC PATCH v3 05/10] ima/ima_boot_aggregate: Increase MAX_EVENT_SIZE to 1MB Petr Vorel
2018-04-20 11:02 ` Cyril Hrubis
2018-04-19 19:54 ` [LTP] [RFC PATCH v3 06/10] ima/tpm.sh: Use evmctl + other fixes Petr Vorel
2018-04-19 19:55 ` [LTP] [RFC PATCH v3 07/10] ima/ima_mmap: Reduce sleep + log it Petr Vorel
2018-04-20 11:36 ` Cyril Hrubis
2018-04-19 19:55 ` [LTP] [RFC PATCH v3 08/10] ima/{ima_measurements, ima_violations}.sh: Avoid running on tmpfs Petr Vorel
2018-04-19 19:55 ` [LTP] [RFC PATCH v3 09/10] ima: CRYPTO_LIBS are needed only for ima_boot_aggregate Petr Vorel
2018-04-19 19:55 ` [LTP] [RFC PATCH v3 10/10] ima/ima_mmap: Rewrite to new library Petr Vorel
2018-04-20 11:42 ` Cyril Hrubis
2018-04-26 16:18 ` [LTP] [RFC PATCH v3 00/10] Rewrite tests into new API + fixes Mimi Zohar
2018-04-27 9:32 ` Petr Vorel
2018-04-27 9:51 ` Petr Vorel
2018-04-27 11:26 ` Mimi Zohar
2018-04-27 12:05 ` Mimi Zohar
2018-04-27 12:51 ` 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=20180427000327.GA25413@x230 \
--to=pvorel@suse.cz \
--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