From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Vincent Abraham <vincent.ahm@gmail.com>
Subject: Re: Comprehensive Documentation on the Linux Audit Framework
Date: Mon, 05 Jun 2023 17:28:10 -0400 [thread overview]
Message-ID: <3244111.44csPzL39Z@x2> (raw)
In-Reply-To: <CAMKmEH-s9kZn5kqkjb_QHA2X02TWX+utqu365-7cRKMM7E5eVQ@mail.gmail.com>
On Monday, June 5, 2023 6:17:28 PM EDT Vincent Abraham wrote:
> Greetings,
> Could anyone point me to a source for comprehensive documentation for the
> Linux audit framework? I want to know how the framework interacts with the
> kernel to retrieve log information.
If you look at the README page of the userspace portion of code, it mentions
that there is a netlink api. It simply listens and writes what it finds to
disk. Auditing must be enabled and you need to set the pid in the kernel and
then listen for events. There is no extensive documentation - the code is the
documentation to the low level API.
There is also a best effort multicast netlink api that systemd-journald uses
to get events out of the kernel.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2023-06-05 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMKmEH-s9kZn5kqkjb_QHA2X02TWX+utqu365-7cRKMM7E5eVQ@mail.gmail.com>
2023-06-05 18:46 ` Comprehensive Documentation on the Linux Audit Framework Richard Guy Briggs
2023-06-05 21:28 ` Steve Grubb [this message]
[not found] ` <ZH5VgjpTytqaj5i5@madcap2.tricolour.ca>
[not found] ` <CAMKmEH_hfOO_9a=QmUC9dQezA_hn0Kj-78hsK5GpXFbNXx2G_w@mail.gmail.com>
2023-06-06 19:08 ` Steve Grubb
2023-06-06 22:01 ` Paul Moore
2023-06-07 2:31 ` Richard Guy Briggs
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=3244111.44csPzL39Z@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=vincent.ahm@gmail.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;
as well as URLs for NNTP newsgroup(s).