From: Mimi Zohar <zohar@linux.vnet.ibm.com> To: Petr Vorel <pvorel@suse.cz>, ltp@lists.linux.it Cc: linux-integrity@vger.kernel.org Subject: Re: [RFC PATCH v2 1/4] security/ima: Rewrite tests into new API + fixes Date: Tue, 27 Mar 2018 15:12:31 -0400 [thread overview] Message-ID: <1522177951.3541.180.camel@linux.vnet.ibm.com> (raw) In-Reply-To: <20180314155731.5943-2-pvorel@suse.cz> On Wed, 2018-03-14 at 16:57 +0100, Petr Vorel wrote: > * simplify code, remove duplicity > > * ima_measurements.sh: > - add support for "ima-ng" and "ima-sig" IMA measurement templates > - add support for most of hash algorithms is defined in > include/uapi/linux/hash_info.h (kernel headers); algorithms are > detected from last occurance of tested file in > /sys/kernel/security/ima/ascii_runtime_measurements > - check i_version mount option only for ext[2-4] filesystems (other > filesystems don't report it), TCONF when not mounted with it > - XFS has iversion support from >= V5, TCONF when older version Needing the filesystem to be mounted with i_version is changing in Linux 4.16. With commit ac0bf025d2c0 ("ima: Use i_version only when filesystem supports it"), files on filesystems, which do not support i_version, will now *always* be re-measured (based on policy), making i_version a performance improvement. [...] > load_policy() > { > + local ret > + > exec 2>/dev/null 4>$IMA_POLICY > - if [ $? -ne 0 ]; then > - exit 1 > - fi > + [ $? -eq 0 ] || exit 1 > > cat $1 | > - while read line ; do > - { > - if [ "${line#\#}" = "${line}" ] ; then > - echo $line >&4 2> /dev/null > + while read line; do > + if [ "${line#\#}" = "${line}" ]; then > + echo "$line" >&4 2> /dev/null > if [ $? -ne 0 ]; then > exec 4>&- > return 1 > fi > fi > - } Originally writing the policy was done one rule at a time, but hasn't been required for a long time. dracut and systemd 'cat' the policy directly to the pseudo file. Mimi
WARNING: multiple messages have this Message-ID (diff)
From: Mimi Zohar <zohar@linux.vnet.ibm.com> To: ltp@lists.linux.it Subject: [LTP] [RFC PATCH v2 1/4] security/ima: Rewrite tests into new API + fixes Date: Tue, 27 Mar 2018 15:12:31 -0400 [thread overview] Message-ID: <1522177951.3541.180.camel@linux.vnet.ibm.com> (raw) In-Reply-To: <20180314155731.5943-2-pvorel@suse.cz> On Wed, 2018-03-14 at 16:57 +0100, Petr Vorel wrote: > * simplify code, remove duplicity > > * ima_measurements.sh: > - add support for "ima-ng" and "ima-sig" IMA measurement templates > - add support for most of hash algorithms is defined in > include/uapi/linux/hash_info.h (kernel headers); algorithms are > detected from last occurance of tested file in > /sys/kernel/security/ima/ascii_runtime_measurements > - check i_version mount option only for ext[2-4] filesystems (other > filesystems don't report it), TCONF when not mounted with it > - XFS has iversion support from >= V5, TCONF when older version Needing the filesystem to be mounted with i_version is changing in Linux 4.16. With commit ac0bf025d2c0 ("ima: Use i_version only when filesystem supports it"), files on filesystems, which do not support i_version, will now *always* be re-measured (based on policy), making i_version a performance improvement. [...] > load_policy() > { > + local ret > + > exec 2>/dev/null 4>$IMA_POLICY > - if [ $? -ne 0 ]; then > - exit 1 > - fi > + [ $? -eq 0 ] || exit 1 > > cat $1 | > - while read line ; do > - { > - if [ "${line#\#}" = "${line}" ] ; then > - echo $line >&4 2> /dev/null > + while read line; do > + if [ "${line#\#}" = "${line}" ]; then > + echo "$line" >&4 2> /dev/null > if [ $? -ne 0 ]; then > exec 4>&- > return 1 > fi > fi > - } Originally writing the policy was done one rule at a time, but hasn't been required for a long time. dracut and systemd 'cat' the policy directly to the pseudo file. Mimi
next prev parent reply other threads:[~2018-03-27 19:12 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-14 15:57 [RFC PATCH v2 0/4] Rewrite tests into new API + fixes Petr Vorel 2018-03-14 15:57 ` [LTP] " Petr Vorel 2018-03-14 15:57 ` [RFC PATCH v2 1/4] security/ima: " Petr Vorel 2018-03-14 15:57 ` [LTP] " Petr Vorel 2018-03-14 16:32 ` Petr Vorel 2018-03-14 16:32 ` [LTP] " Petr Vorel 2018-03-27 19:12 ` Mimi Zohar [this message] 2018-03-27 19:12 ` Mimi Zohar 2018-03-29 8:59 ` Petr Vorel 2018-03-29 8:59 ` [LTP] " Petr Vorel 2018-04-10 15:56 ` Mimi Zohar 2018-04-10 15:56 ` [LTP] " Mimi Zohar 2018-04-11 19:03 ` Petr Vorel 2018-04-11 19:03 ` [LTP] " Petr Vorel 2018-04-11 20:03 ` Mimi Zohar 2018-04-11 20:03 ` [LTP] " Mimi Zohar 2018-03-14 15:57 ` [RFC PATCH v2 2/4] security/ima: Run measurements after policy Petr Vorel 2018-03-14 15:57 ` [LTP] " Petr Vorel 2018-03-14 15:57 ` [RFC PATCH v2 3/4] ima/ima_boot_aggregate: Increase MAX_EVENT_SIZE to 8k Petr Vorel 2018-03-14 15:57 ` [LTP] " Petr Vorel 2018-03-27 19:44 ` Mimi Zohar 2018-03-27 19:44 ` [LTP] " Mimi Zohar 2018-03-27 22:23 ` George Wilson 2018-03-29 6:18 ` Petr Vorel 2018-03-29 6:18 ` [LTP] " Petr Vorel 2018-03-14 15:57 ` [RFC PATCH v2 4/4] ima/tpm: Various fixes Petr Vorel 2018-03-14 15:57 ` [LTP] " Petr Vorel 2018-03-26 22:31 ` [RFC PATCH v2 0/4] Rewrite tests into new API + fixes Mimi Zohar 2018-03-26 22:31 ` [LTP] " Mimi Zohar 2018-03-27 9:22 ` Petr Vorel 2018-03-27 9:22 ` [LTP] " 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=1522177951.3541.180.camel@linux.vnet.ibm.com \ --to=zohar@linux.vnet.ibm.com \ --cc=linux-integrity@vger.kernel.org \ --cc=ltp@lists.linux.it \ --cc=pvorel@suse.cz \ /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: linkBe 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.