public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Kay Hayen <kayhayen@gmx.de>
Cc: linux-audit@redhat.com, alex@segv.de
Subject: Re: Audit for live supervision
Date: Tue, 19 Aug 2008 14:18:46 -0400	[thread overview]
Message-ID: <200808191418.46608.sgrubb@redhat.com> (raw)
In-Reply-To: <200808191946.14420.kayhayen@gmx.de>

On Tuesday 19 August 2008 13:46:14 Kay Hayen wrote:
> > No, you really want to use the user space interface (see above).
>
> Well, for lowest latency possible (note the "live" in subject), it would be
> ideal to avoid context switches auditd -> audisp -> our supervisor and
> instead simply run an additional netlink socket in addition to auditd (if
> that is allowed). That way we would have a lot less latency, at least in
> theory.

Only 1 netlink socket connection is allowed. The code you want to write for 
low latency would either need to take the place of the audit daemon, meaning 
you need to make your own trail if you need it. Or, write an audispd that is 
run from auditd. There is some sample code here contrib/skeleton.c for 
starting your own audispd.

-Steve

  reply	other threads:[~2008-08-19 18:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-14  7:14 Audit for live supervision Kay Hayen
2008-08-14 14:04 ` Steve Grubb
2008-08-15  6:43   ` Kay Hayen
2008-08-15 12:54     ` Steve Grubb
2008-08-16 11:19       ` Kay Hayen
2008-08-18 15:10         ` Steve Grubb
2008-08-19  6:45           ` Kay Hayen
2008-08-19 14:14             ` John Dennis
2008-08-19 17:46               ` Kay Hayen
2008-08-19 18:18                 ` Steve Grubb [this message]
2008-08-19 14:47             ` Steve Grubb
2008-08-19 18:23               ` Kay Hayen
2008-08-19 18:39                 ` Steve Grubb
2008-08-19 20:33                   ` Kay Hayen
2008-08-19 20:47                     ` Steve Grubb
2008-08-19 21:35                       ` Kay Hayen
2008-08-19 21:47                         ` Steve Grubb

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=200808191418.46608.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=alex@segv.de \
    --cc=kayhayen@gmx.de \
    --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