linux-audit.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: fw@strlen.de, LKML <linux-kernel@vger.kernel.org>,
	Linux-Audit Mailing List <linux-audit@redhat.com>,
	netfilter-devel@vger.kernel.org, twoerner@redhat.com,
	Eric Paris <eparis@parisplace.org>,
	tgraf@infradead.org
Subject: Re: [PATCH ghak25 v5] audit: add subj creds to NETFILTER_CFG record to cover async unregister
Date: Tue, 19 May 2020 15:59:05 -0400	[thread overview]
Message-ID: <CAHC9VhQRSwTURYZ2dL_YWqi-xnPfFGN_Aef73mip=eYNVfObRw@mail.gmail.com> (raw)
In-Reply-To: <20200519194457.nouzteqv2vpcqnta@madcap2.tricolour.ca>

On Tue, May 19, 2020 at 3:45 PM Richard Guy Briggs <rgb@redhat.com> wrote:
> On 2020-05-19 15:18, Paul Moore wrote:
> > On Tue, May 19, 2020 at 11:31 AM Richard Guy Briggs <rgb@redhat.com> wrote:
> > > Some table unregister actions seem to be initiated by the kernel to
> > > garbage collect unused tables that are not initiated by any userspace
> > > actions.  It was found to be necessary to add the subject credentials to
> > > cover this case to reveal the source of these actions.  A sample record:
> > >
> > > The tty, ses and exe fields have not been included since they are in the
> > > SYSCALL record and contain nothing useful in the non-user context.
> > >
> > >   type=NETFILTER_CFG msg=audit(2020-03-11 21:25:21.491:269) : table=nat family=bridge entries=0 op=unregister pid=153 uid=root auid=unset subj=system_u:system_r:kernel_t:s0 comm=kworker/u4:2
> >
> > Based on where things were left in the discussion on the previous
> > draft, I think it would be good if you could explain a bit why the uid
> > and auid fields are useful here.
>
> They aren't really useful here.  I was hoping to remove them given your
> reasoning, but I was having trouble guessing what you wanted even after
> asking for clarity.  Can you clarify what you would prefer to see in
> this patch?

/me heavily rolls eyes

In my last email to you I said:

"I think it is pointless to record the subject info in this record as we
either have that info from other records in the event or there is no
valid subject info to record."

... I also said:

"As I've mentioned in the thread above, including the auid was done as
a concession to Steve, I don't think it serves any useful purpose."

If phrases like "pointless to record the subject info" and "I don't
think it serves any useful purpose" leave you unsure about what to do,
I'm at a bit of a loss.

Drop the "uid" field.  Drop the "auid" field.  Hopefully those last
two statements should remove any ambiguity from your mind.

-- 
paul moore
www.paul-moore.com

--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit


      reply	other threads:[~2020-05-19 19:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 15:30 [PATCH ghak25 v5] audit: add subj creds to NETFILTER_CFG record to cover async unregister Richard Guy Briggs
2020-05-19 19:18 ` Paul Moore
2020-05-19 19:44   ` Richard Guy Briggs
2020-05-19 19:59     ` Paul Moore [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='CAHC9VhQRSwTURYZ2dL_YWqi-xnPfFGN_Aef73mip=eYNVfObRw@mail.gmail.com' \
    --to=paul@paul-moore.com \
    --cc=eparis@parisplace.org \
    --cc=fw@strlen.de \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=rgb@redhat.com \
    --cc=tgraf@infradead.org \
    --cc=twoerner@redhat.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).