From: Eric Paris <eparis@redhat.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, James Morris <jmorris@namei.org>,
david safford <safford@watson.ibm.com>
Subject: Re: [PATCH] integrity: use audit_log_string
Date: Tue, 05 May 2009 13:59:20 -0400 [thread overview]
Message-ID: <1241546360.1997.0.camel@dhcp231-142.rdu.redhat.com> (raw)
In-Reply-To: <1241543580.6101.11.camel@dyn9002018117.watson.ibm.com>
On Tue, 2009-05-05 at 13:13 -0400, Mimi Zohar wrote:
> Based on a request from Eric Paris to simplify parsing, replace
> audit_log_format statements containing "%s" with audit_log_string().
>
> Signed-off-by: Mimi Zohar <zohar@us.ibm.com>
As long as you don't mind that change from hash= to cause= I'm ok with
it too:
Acked-by: Eric Paris <eparis@redhat.com>
>
> Index: security-testing-2.6/security/integrity/ima/ima_audit.c
> ===================================================================
> --- security-testing-2.6.orig/security/integrity/ima/ima_audit.c
> +++ security-testing-2.6/security/integrity/ima/ima_audit.c
> @@ -54,19 +54,10 @@ void integrity_audit_msg(int audit_msgno
> audit_get_loginuid(current),
> audit_get_sessionid(current));
> audit_log_task_context(ab);
> - switch (audit_msgno) {
> - case AUDIT_INTEGRITY_DATA:
> - case AUDIT_INTEGRITY_METADATA:
> - case AUDIT_INTEGRITY_PCR:
> - case AUDIT_INTEGRITY_STATUS:
> - audit_log_format(ab, " op=%s cause=%s", op, cause);
> - break;
> - case AUDIT_INTEGRITY_HASH:
> - audit_log_format(ab, " op=%s hash=%s", op, cause);
> - break;
> - default:
> - audit_log_format(ab, " op=%s", op);
> - }
> + audit_log_format(ab, " op=");
> + audit_log_string(ab, op);
> + audit_log_format(ab, " cause=");
> + audit_log_string(ab, cause);
> audit_log_format(ab, " comm=");
> audit_log_untrustedstring(ab, current->comm);
> if (fname) {
>
>
prev parent reply other threads:[~2009-05-05 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 17:13 Mimi Zohar
2009-05-05 17:59 ` Eric Paris [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=1241546360.1997.0.camel@dhcp231-142.rdu.redhat.com \
--to=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=safford@watson.ibm.com \
--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
all inboxes | Powered by JetHome®