From: Miloslav Trmac <mitr@redhat.com>
To: George McCollister <george.mccollister@gmail.com>
Cc: linux-audit@redhat.com
Subject: Re: Thoughts on adding sd-journal as a log_format to auditd
Date: Fri, 15 Mar 2013 11:22:50 -0400 (EDT) [thread overview]
Message-ID: <1738104947.8168390.1363360970843.JavaMail.root@redhat.com> (raw)
In-Reply-To: <CAFSKS=M_aNrjq7fF2A_9m2f9cJn2FX1jPsoaBnwb4DDfvR0YDg@mail.gmail.com>
----- Original Message -----
> 2) Write an audispd plugin that used the sd-journal API to store
> audit events in the journal.
>
> 3) Add sd-journal as a log format to auditd.
Both of these will run into the problem recently discussed on this mailing list: the available methods to parse an audit records into fields are a bit imprecise/"lossy" because not all records keep the name=value format as expected.
This can be OK if auparse is able to extract all the data you need/expect to process.
Mirek
next prev parent reply other threads:[~2013-03-15 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 14:43 Thoughts on adding sd-journal as a log_format to auditd George McCollister
2013-03-15 15:22 ` Miloslav Trmac [this message]
2013-03-15 16:54 ` Steve Grubb
2013-03-20 20:58 ` Eric Paris
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=1738104947.8168390.1363360970843.JavaMail.root@redhat.com \
--to=mitr@redhat.com \
--cc=george.mccollister@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