All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Klaus Heinrich Kiwi <klausk@br.ibm.com>
Subject: Re: Audit plug-ins development
Date: Tue, 7 Aug 2007 17:28:49 -0400	[thread overview]
Message-ID: <200708071728.50323.sgrubb@redhat.com> (raw)
In-Reply-To: <f99ufv$7lj$1@sea.gmane.org>

On Tuesday 07 August 2007 10:10:07 am Klaus Heinrich Kiwi wrote:
>  I'm interested in developing an audit plug-in to forward events to z/OS
> RACF (sort of a centralized AAA facility for IBM System Z systems).

Nice.

> What is your general idea for audit plug-ins deploymet?

You would drop a config file into /etc/audisp/plugins.d and it contains the 
information to tell the dispatcher what to do. I think there are a couple in 
audit-1.5.7/new_audispd/configs to look at for an example.

> Would we be able to contribute the plug-ins to the audit userspace so that
> they can be available in the audit source package, and then maybe in a
> separate binary package upon building?

That sounds good unless...

> Can you give us some hints about how would you want this code contributions
> and how would you want these blended in the audit tree?

I'm wanting to keep the audit code GPLv2+ and the libraries LGPLv2+ so that if 
there is any compelling reason to change licenses that the project can do 
that. But I don't have any immediate plans to change to v3 right now.

I would like to just create a plugins directory under audit-1.5.7/new_audispd 
and then each plugin under that. I'm looking to move the project to Feodora's 
cvs facilities sometime soon. So, maybe the 1.5.8 release I could merge any 
plugins? I also need to do a quick write-up for what is expected of a plugin 
before I start accepting them.

-Steve

      reply	other threads:[~2007-08-07 21:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 14:10 Audit plug-ins development Klaus Heinrich Kiwi
2007-08-07 21:28 ` 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=200708071728.50323.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=klausk@br.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.