From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Filtering out non-interactive users
Date: Wed, 19 Jan 2011 10:04:11 -0500 [thread overview]
Message-ID: <201101191004.11802.sgrubb@redhat.com> (raw)
In-Reply-To: <20110119144824.GA7022@monolith>
On Wednesday, January 19, 2011 09:48:25 am PJB wrote:
> On Wed, Jan 19, 2011 at 09:33:30AM -0500, Steve Grubb [sgrubb@redhat.com] wrote:
> > On Wednesday, January 19, 2011 09:01:55 am PJB wrote:
> > > > That should work unless the is a 32 bit bug everyone has missed or
> > > > you have another rule preventing the logging. If you do cat
> > > > /proc/self/loginuid, do you get a number > 0? Also, if you use
> > > > auid!=4294967295, does that work?
> > >
> > > The loginuid is 4294967295. If I pass '-F auid!=4294967295' into the
> > > filters, when I run 'auditctl -l' the rules are listed, but each one
> > > has 'auid=2147483647 (0x7fffffff)'. I get log entries then, but they
> > > are all tagged with auid 4294967295. Is this proper or did I stumble
> > > upon a bug after all?
> >
> > That is a 32 bit bug. I'm looking at how best to solve this. Probably all
> > variants of uid and gid are affected by this.
>
> I was afraid you would say that! Would it be a bug in the auditd userspace
> programs or in the kernel code? I assume it's the former?
Specifically, the bug is right here:
https://fedorahosted.org/audit/browser/trunk/lib/libaudit.c#L1134
AUID on 32 bit should be treated like the AUDIT_INODE field. Still looking at it...
-Steve
next prev parent reply other threads:[~2011-01-19 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 16:37 Filtering out non-interactive users PJB
2011-01-14 22:21 ` Steve Grubb
2011-01-16 1:39 ` PJB
2011-01-16 15:00 ` Steve Grubb
2011-01-19 14:01 ` PJB
2011-01-19 14:33 ` Steve Grubb
2011-01-19 14:48 ` PJB
2011-01-19 15:04 ` Steve Grubb [this message]
2011-01-20 19:28 ` Steve Grubb
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=201101191004.11802.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@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