public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com, Miloslav Trmac <mitr@redhat.com>
Subject: Re: Thoughts on adding sd-journal as a log_format to auditd
Date: Wed, 20 Mar 2013 16:58:53 -0400	[thread overview]
Message-ID: <1363813133.2333.21.camel@localhost> (raw)
In-Reply-To: <1416476.vdemb8vVx9@x2>

On Fri, 2013-03-15 at 12:54 -0400, Steve Grubb wrote:
> On Friday, March 15, 2013 11:22:50 AM Miloslav Trmac wrote:
> > ----- 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.
> 
> I don't think this is a problem to worry about. A plugin is handed the whole 
> event line by line. To push events you don't need to parse. The real issue is 
> later...running reports.
> 
> I also thought there was some patch presented on this list sometime in the 
> last month to allow journald to listen for audit events directly.

That's correct.  There is work to pass audit messages directly from the
kernel to the journal.  But it isn't ready.  Today, your best bet if you
are doing it yourself is any of the above, but I don't know which one...

      reply	other threads:[~2013-03-20 20:58 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
2013-03-15 16:54   ` Steve Grubb
2013-03-20 20:58     ` Eric Paris [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=1363813133.2333.21.camel@localhost \
    --to=eparis@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=mitr@redhat.com \
    --cc=sgrubb@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