From: Paul Moore <paul@paul-moore.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: Steve Grubb <sgrubb@redhat.com>,
Stefan Berger <stefanb@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org, linux-audit@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/8] integrity: Add exe= and tty= before res= to integrity audits
Date: Wed, 30 May 2018 17:15:58 -0400 [thread overview]
Message-ID: <CAHC9VhRNoB+B46QkRSbc9CwRRdgTHw1sLQ+ccipvqk1PVUw70g@mail.gmail.com> (raw)
In-Reply-To: <1527685480.3534.54.camel@linux.vnet.ibm.com>
On Wed, May 30, 2018 at 9:04 AM, Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:
> On Tue, 2018-05-29 at 18:58 -0400, Mimi Zohar wrote:
>> On Tue, 2018-05-29 at 17:47 -0400, Paul Moore wrote:
>> > On Tue, May 29, 2018 at 5:35 PM, Steve Grubb <sgrubb@redhat.com> wrote:
>> > > On Tuesday, May 29, 2018 5:19:39 PM EDT Paul Moore wrote:
>> > >> On Thu, May 24, 2018 at 4:11 PM, Stefan Berger
>> > >>
>> > >> <stefanb@linux.vnet.ibm.com> wrote:
>> > >> > Use the new public audit functions to add the exe= and tty=
>> > >> > parts to the integrity audit records. We place them before
>> > >> > res=.
>> > >> >
>> > >> > Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
>> > >> > Suggested-by: Steve Grubb <sgrubb@redhat.com>
>> > >> > ---
>> > >> >
>> > >> > security/integrity/integrity_audit.c | 2 ++
>> > >> > 1 file changed, 2 insertions(+)
>> > >> >
>> > >> > diff --git a/security/integrity/integrity_audit.c
>> > >> > b/security/integrity/integrity_audit.c index db30763d5525..8d25d3c4dcca
>> > >> > 100644
>> > >> > --- a/security/integrity/integrity_audit.c
>> > >> > +++ b/security/integrity/integrity_audit.c
>> > >> > @@ -56,6 +56,8 @@ void integrity_audit_msg(int audit_msgno, struct inode
>> > >> > *inode,>
>> > >> > audit_log_untrustedstring(ab, inode->i_sb->s_id);
>> > >> > audit_log_format(ab, " ino=%lu", inode->i_ino);
>> > >> >
>> > >> > }
>> > >> >
>> > >> > + audit_log_d_path_exe(ab, current->mm);
>> > >> > + audit_log_tty(ab, current);
>> > >>
>> > >> NACK
>> > >>
>> > >> Please add the new fields to the end of the audit record, thank you.
>> > >
>> > > Let's see what an example event looks like before NACK'ing this. Way back in
>> > > 2013 the IMA events were good. I think this is repairing the event after some
>> > > drift.
>> >
>> > Can you reference a specific commit, or point in time during 2013?
>> > Looking at the git log quickly, if I go back to commit d726d8d719b6
>> > ("integrity: move integrity_audit_msg()") from March 18, 2013 (the
>> > commit that created integrity_audit.c) the field ordering appears to
>> > be the same as it today.
>> >
>> > My NACK still stands.
>>
>> There hasn't been any changes up to now. This patch set refactors
>> integrity_audit_msg(), creating integrity_audit_msg_common(), which
>> will be called from both ima_audit_measurement() and
>> ima_parse_rule().
>
> That should have been "from integrity_audit_msg() and
> ima_parse_rule()", not ima_audit_measurement().
No worries, the important part is that the record format really hasn't
changed from 2013 as far as I can tell.
>> Previously the audit record generated by ima_parse_rule() did not
>> include this info. The change in this patch will affect both the
>> existing and the new INTEGRITY_AUDIT_POLICY_RULE audit records.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2018-05-30 21:16 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 20:10 [PATCH 0/8] IMA: work on audit records produced by IMA Stefan Berger
2018-05-24 20:10 ` [PATCH 1/8] ima: Call audit_log_string() rather than logging it untrusted Stefan Berger
2018-05-29 20:29 ` Paul Moore
2018-05-24 20:10 ` [PATCH 2/8] ima: Use audit_log_format() rather than audit_log_string() Stefan Berger
2018-05-29 20:31 ` Paul Moore
2018-05-24 20:11 ` [PATCH 3/8] audit: Implement audit_log_tty() Stefan Berger
2018-05-29 21:07 ` Paul Moore
2018-05-30 19:46 ` Stefan Berger
2018-05-24 20:11 ` [PATCH 4/8] audit: Allow others to call audit_log_d_path_exe() Stefan Berger
2018-05-29 21:18 ` Paul Moore
2018-05-24 20:11 ` [PATCH 5/8] integrity: Add exe= and tty= before res= to integrity audits Stefan Berger
2018-05-29 21:19 ` Paul Moore
2018-05-29 21:35 ` Steve Grubb
2018-05-29 21:47 ` Paul Moore
2018-05-29 22:58 ` Mimi Zohar
2018-05-30 13:04 ` Mimi Zohar
2018-05-30 21:15 ` Paul Moore [this message]
2018-05-30 12:17 ` Stefan Berger
2018-05-30 21:14 ` Paul Moore
2018-05-24 20:11 ` [PATCH 6/8] integrity: Factor out common part of integrity_audit_msg() Stefan Berger
2018-05-29 21:32 ` Steve Grubb
2018-05-30 13:04 ` Stefan Berger
2018-05-24 20:11 ` [PATCH 7/8] ima: Do not audit if CONFIG_INTEGRITY_AUDIT is not set Stefan Berger
2018-05-24 20:11 ` [PATCH 8/8] ima: Differentiate auditing policy rules from "audit" actions Stefan Berger
2018-05-29 21:30 ` Steve Grubb
[not found] ` <2d5baf73-755b-dc82-a778-25a3cd22989a@linux.vnet.ibm.com>
2018-05-30 15:15 ` Steve Grubb
2018-05-30 15:25 ` Stefan Berger
2018-05-30 16:27 ` Steve Grubb
2018-05-30 19:54 ` Stefan Berger
2018-05-30 21:24 ` Paul Moore
2018-05-30 21:49 ` Stefan Berger
2018-05-30 22:00 ` Mimi Zohar
2018-05-30 22:15 ` Stefan Berger
2018-05-30 22:41 ` Mimi Zohar
2018-05-30 23:54 ` Paul Moore
2018-05-30 12:49 ` Richard Guy Briggs
2018-05-30 12:55 ` Steve Grubb
2018-05-30 13:08 ` Stefan Berger
2018-05-30 21:22 ` Paul Moore
2018-05-30 21:38 ` Stefan Berger
2018-05-30 23:34 ` Richard Guy Briggs
2018-06-01 20:00 ` Stefan Berger
2018-06-01 20:13 ` Paul Moore
2018-06-01 20:21 ` Paul Moore
2018-06-01 20:50 ` Stefan Berger
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=CAHC9VhRNoB+B46QkRSbc9CwRRdgTHw1sLQ+ccipvqk1PVUw70g@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=linux-audit@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sgrubb@redhat.com \
--cc=stefanb@linux.vnet.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;
as well as URLs for NNTP newsgroup(s).