Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: euid missing
Date: Wed, 13 Jul 2016 12:39:40 -0400	[thread overview]
Message-ID: <4373501.sMjiJxmkID@x2> (raw)
In-Reply-To: <CAHcE2wp8nCcqfeUMLd6pHuqWfKYbGFm67+w6S1DipoiO0Bf0pA@mail.gmail.com>

On Wednesday, July 13, 2016 9:27:25 AM EDT Chris Nandor wrote:
> As mentioned in previous e-mail, we want to log what users do as root.  I
> have these two rules, only:
> 
> -a exit,always -F arch=b32 -F euid=0 -F auid>=0 -F auid!=4294967295 -S
> execve -k rootcmd
> -a exit,always -F arch=b64 -F euid=0 -F auid>=0 -F auid!=4294967295 -S
> execve -k rootcmd
> 
> But this line shows up:
> 
> node=grax.sea.marchex.com type=ANOM_ABEND
> msg=audit(1468426871.752:3282575): auid=811 uid=811 gid=811 ses=12
> pid=18504 comm="chromium-browse" reason="seccomp" sig=0 syscall=91 compat=0
> ip=0x7f296c759c77 code=0x50001

There are two kinds of events. There are the ones that are triggered by the 
rules you load, and there are rules that are hardwired to be logged because 
something significant happened. In this case the seccomp filter killed 
chromium-browse because it violated policy. It has nothing to do with your 
rules which have a rootcmd key.

To find the events triggered by your rule, use:
ausearch --start today -k rootcmd -i

-Steve

> My guess is that it is because euid is missing; maybe euid=0 is true if
> euid is null?  I could put uid=0, instead of euid ... but that isn't
> exactly what I want, I think.  Is there a way to have the rule require euid
> actually be 0?
> 
> --Chris

  reply	other threads:[~2016-07-13 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13 16:27 euid missing Chris Nandor
2016-07-13 16:39 ` Steve Grubb [this message]
2016-07-13 16:51   ` Chris Nandor

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=4373501.sMjiJxmkID@x2 \
    --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