From: Matthew Garrett <mjg59@google.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: Mimi Zohar <zohar@linux.ibm.com>, Steve Grubb <sgrubb@redhat.com>,
Paul Moore <paul@paul-moore.com>,
linux-integrity <linux-integrity@vger.kernel.org>,
LSM List <linux-security-module@vger.kernel.org>,
Linux-Audit Mailing List <linux-audit@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
omosnace@redhat.com, Eric Paris <eparis@parisplace.org>,
Serge Hallyn <serge@hallyn.com>
Subject: Re: [PATCH ghak109 V1] audit: link integrity evm_write_xattrs record to syscall event
Date: Tue, 26 Mar 2019 10:55:57 -0700 [thread overview]
Message-ID: <CACdnJusGS94GTVkGO1xsczdksBVEf39A7z-H36tWNDo5xwobqQ@mail.gmail.com> (raw)
In-Reply-To: <20190326174252.irqrldtcy5bwho6k@madcap2.tricolour.ca>
On Tue, Mar 26, 2019 at 10:43 AM Richard Guy Briggs <rgb@redhat.com> wrote:
> Ok, what I typed above wasn't quite what I intended... This is what I
> meant:
>
> audit_log_format(ab, "xattr=");
> audit_log_untrustedstring(ab, ".");
>
> But, I'll just move the normal case above the "." locking detection and
> log all cases the same way.
Sounds good to me.
prev parent reply other threads:[~2019-03-26 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 12:10 [PATCH ghak109 V1] audit: link integrity evm_write_xattrs record to syscall event Richard Guy Briggs
2019-03-20 23:48 ` Paul Moore
2019-03-21 0:50 ` Richard Guy Briggs
2019-03-21 1:03 ` Paul Moore
2019-03-26 15:11 ` Mimi Zohar
2019-03-26 15:22 ` Steve Grubb
2019-03-26 15:29 ` Mimi Zohar
2019-03-26 16:14 ` Richard Guy Briggs
2019-03-26 17:42 ` Richard Guy Briggs
2019-03-26 17:55 ` Matthew Garrett [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=CACdnJusGS94GTVkGO1xsczdksBVEf39A7z-H36tWNDo5xwobqQ@mail.gmail.com \
--to=mjg59@google.com \
--cc=eparis@parisplace.org \
--cc=linux-audit@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=rgb@redhat.com \
--cc=serge@hallyn.com \
--cc=sgrubb@redhat.com \
--cc=zohar@linux.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;
as well as URLs for NNTP newsgroup(s).