public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Valdis.Kletnieks@vt.edu
Subject: Re: Way too many logs!
Date: Sat, 10 May 2008 21:17:57 -0400	[thread overview]
Message-ID: <200805102117.58187.sgrubb@redhat.com> (raw)
In-Reply-To: <21796.1210368544@turing-police.cc.vt.edu>

On Friday 09 May 2008 17:29:04 Valdis.Kletnieks@vt.edu wrote:
> On Fri, 09 May 2008 16:20:44 EDT, Jeremy Leonard said:
> > -a exit,always -S sched_setparam -S sched_setscheduler -k RULE7
> >
> > type=SYSCALL msg=audit(04/25/08 16:37:48.568:194518) : arch=i386
> > syscall=_newselect
>
> OK, I'll bite - why is a select() syscall tripping sched_setparam or
> sched_setschdeduler?

This record has a personality bit set unlike most events I ever see:

"arch=i386 syscall=_newselect per=400000"

I don't know if that is affecting the syscalls or not. Assuming it doesn't, 
_newselect only occurs on ppc as far as I know. Its syscall 142. On x86_64, 
sched_setparam is syscall 142. Not sure if that is the connection or not. But 
something is wrong in this audit event. :)  Also notice that the subject is 
unconstrained, so they must be running some special SE Linux policy or have a 
very unique kernel.

> Or more importantly - are those two cutting audit events for the wrong
> reasons?

Yeah, could be. I think I'd also want to audit the setting of the personality 
as that could be an attempt at masking the real actions of the user. Most 
systems never do this. If you have a system doing it, you might want to keep 
an eye on that.

-Steve

  reply	other threads:[~2008-05-11  1:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 20:20 Way too many logs! Jeremy Leonard
2008-05-09 20:43 ` Steve Grubb
2008-05-11  0:41   ` Steve Grubb
2008-05-09 21:29 ` Valdis.Kletnieks
2008-05-11  1:17   ` Steve Grubb [this message]
2008-05-26 13:42 ` troy.s.curtis

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=200805102117.58187.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --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