From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: ausearch with message types does not return what I think it would return. (0 matches when adding a user)
Date: Tue, 30 Jun 2015 11:22:17 -0400 [thread overview]
Message-ID: <4397065.b5uXy4mKpJ@x2> (raw)
In-Reply-To: <23396023F719ED41888885C3B22D602F0123D1@WPEXCH2010MR21.bur.hydro.qc.ca>
On Tuesday, June 30, 2015 03:12:40 PM Alarie, Maxime wrote:
> I am new with auditd, and got some issues..
>
> For example, When I add or delete a user, I cannot see the entry with
> ausearch -m ADD_USER, it returns 0 match, BUT its logging it under
> USER_AUTH. If I do a ausearch -x adduser, ill thee se event audit.log with
> the EXECVE Type:
>
> # ausearch -x useradd | grep titi
> type=EXECVE msg=audit(1435677075.900:49410): argc=2 a0="useradd" a1="titi"
>
> I also tried to find a full description of all message types returned by
> ausearch -m but could not find any.. Any help on this would be
> appreciated as well.
I think we discovered that shadow-utils had messed up the auditing pretty
badly a few months ago. It caused me to write a document[1] that outlines how
its supposed to work so that we can check any and all implementations to make
sure they follow the standard. The shadow-utils in RHEL7.1 was patched to be
correct and I presume the patch should be upstream by now.
So, I believe that is what you are seeing. Shadow-utils is a horrible piece of
code for auditing because there are about 320 places that have audit events
generated. I think upstream made it a little better, but its a huge problem
because all those events have to be correct...and they weren't.
-Steve
[1] - http://people.redhat.com/sgrubb/audit/user-account-lifecycle.txt
prev parent reply other threads:[~2015-06-30 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 15:12 ausearch with message types does not return what I think it would return. (0 matches when adding a user) Alarie, Maxime
2015-06-30 15:22 ` Steve Grubb [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=4397065.b5uXy4mKpJ@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