From: Mimi Zohar <zohar@linux.ibm.com>
To: clayc@hpe.com, linux-kernel@vger.kernel.org
Cc: linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org, dmitry.kasatkin@gmail.com,
jmorris@namei.org, serge@hallyn.com
Subject: Re: [PATCH] ima: Add a space after printing a LSM rule for readability
Date: Fri, 03 Jan 2020 12:11:27 -0500 [thread overview]
Message-ID: <1578071487.5152.13.camel@linux.ibm.com> (raw)
In-Reply-To: <1578037863-7102-1-git-send-email-clayc@hpe.com>
On Fri, 2020-01-03 at 15:51 +0800, clayc@hpe.com wrote:
> From: Clay Chang <clayc@hpe.com>
Normally this "From" line is only seen when the sender isn't the patch
author. Any ideas what happened?
>
> When reading ima_policy from securityfs, there is a missing
> space between output string of LSM rules.
>
> Signed-off-by: Clay Chang <clayc@hpe.com>
Good catch! IMA policy rules based on LSM labels are used to
constrain which files are in policy. Normally a single LSM label is
enough (e.g. dont_measure obj_type=auditd_log_t). Could you include
in this patch description a use case where multiple LSM labels are
needed?
thanks,
Mimi
> ---
> security/integrity/ima/ima_policy.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/security/integrity/ima/ima_policy.c b/security/integrity/ima/ima_policy.c
> index ef8dfd47c7e3..1a266e4f99bc 100644
> --- a/security/integrity/ima/ima_policy.c
> +++ b/security/integrity/ima/ima_policy.c
> @@ -1496,6 +1496,7 @@ int ima_policy_show(struct seq_file *m, void *v)
> (char *)entry->lsm[i].args_p);
> break;
> }
> + seq_puts(m, " ");
> }
> }
> if (entry->template)
next prev parent reply other threads:[~2020-01-03 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 7:51 [PATCH] ima: Add a space after printing a LSM rule for readability clayc
2020-01-03 17:11 ` Mimi Zohar [this message]
2020-01-05 1:12 ` Clay Chang
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=1578071487.5152.13.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=clayc@hpe.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.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