* euid missing
@ 2016-07-13 16:27 Chris Nandor
2016-07-13 16:39 ` Steve Grubb
0 siblings, 1 reply; 3+ messages in thread
From: Chris Nandor @ 2016-07-13 16:27 UTC (permalink / raw)
To: linux-audit
[-- Attachment #1.1: Type: text/plain, Size: 765 bytes --]
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
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
[-- Attachment #1.2: Type: text/html, Size: 1040 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: euid missing
2016-07-13 16:27 euid missing Chris Nandor
@ 2016-07-13 16:39 ` Steve Grubb
2016-07-13 16:51 ` Chris Nandor
0 siblings, 1 reply; 3+ messages in thread
From: Steve Grubb @ 2016-07-13 16:39 UTC (permalink / raw)
To: linux-audit
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: euid missing
2016-07-13 16:39 ` Steve Grubb
@ 2016-07-13 16:51 ` Chris Nandor
0 siblings, 0 replies; 3+ messages in thread
From: Chris Nandor @ 2016-07-13 16:51 UTC (permalink / raw)
To: Steve Grubb; +Cc: linux-audit
[-- Attachment #1.1: Type: text/plain, Size: 1577 bytes --]
Ah, thanks. I had only recently added -k rootcmd so I didn't notice it was
different earlier ... but I should've noticed this time. Thanks!
On Wed, Jul 13, 2016 at 9:39 AM, Steve Grubb <sgrubb@redhat.com> wrote:
> 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
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2279 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-07-13 16:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-07-13 16:27 euid missing Chris Nandor
2016-07-13 16:39 ` Steve Grubb
2016-07-13 16:51 ` Chris Nandor
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox