From: Steve Grubb <sgrubb@redhat.com>
To: William Roberts <bill.c.roberts@gmail.com>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: Definitive guide for audit message types
Date: Sat, 11 Oct 2014 18:01:52 -0400 [thread overview]
Message-ID: <20141011180152.52f65c56@ivy-bridge> (raw)
In-Reply-To: <CAFftDdqFDNVBiwwTnxAGnorKpPL7cDjekxq=0jthBpU0X=SA5A@mail.gmail.com>
On Fri, 10 Oct 2014 09:58:48 -0700
William Roberts <bill.c.roberts@gmail.com> wrote:
> For audit log records, the type field can be something like 1400 for
> an AVC event. I know on the desktop it formats these all to the pretty
> names IIRC, however I am on Android and were not quite as advanced
> yet. Is their a definitive guide for each number what they correspond
> to besides cracking open the header files?
The kernel headers and libaudit headers are the literal definitive
source. They can be seen here:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/include/uapi/linux/audit.h?id=refs/tags/v3.16.5#n30
and
https://fedorahosted.org/audit/browser/trunk/lib/libaudit.h#L40
-Steve
prev parent reply other threads:[~2014-10-11 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 16:58 Definitive guide for audit message types William Roberts
2014-10-11 22:01 ` 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=20141011180152.52f65c56@ivy-bridge \
--to=sgrubb@redhat.com \
--cc=bill.c.roberts@gmail.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