From: LC Bruzenak <lenny@magitekltd.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: prelude events
Date: Mon, 25 Aug 2008 16:03:32 -0500 [thread overview]
Message-ID: <1219698212.7022.821.camel@homeserver> (raw)
In-Reply-To: <1219697258.7022.815.camel@homeserver>
On Mon, 2008-08-25 at 15:47 -0500, LC Bruzenak wrote:
> On Mon, 2008-08-25 at 16:41 -0400, Steve Grubb wrote:
> > On Monday 25 August 2008 16:24:35 LC Bruzenak wrote:
> > > I think I just saw the answer in the audisp-prelude man page:
> > > ...
> > > -w /etc/shadow -p wa
> > >
> > > and you want idmef alerts on this, you need to add -k
> > > ids-file-med or something appropriate to signal to the plugin
> > > that this message is for it.
> >
> > Yes, you'd add -k ids-file- and the one of: info, low, med, or high
> > depending on how severe you consider this access.
> >
> > -Steve
>
> ...and of course then that made me think if we can do this for the file
> watches, why not for user-submitted events also? Some of these I am
> already sending into the prelude system via patched audisp-prelude.c
> code, but I'd prefer to rip out this hack and instead just have a
> matching key identified.
I don't know why I cannot think until after I hit the "send" button...
:)
The problem there is that I still want to build the prelude event with
some added name=value information I stuck in to the audit event text,
which I'd like to see in the prewikka viewer.
LCB.
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
next prev parent reply other threads:[~2008-08-25 21:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 20:20 prelude events LC Bruzenak
2008-08-25 20:24 ` LC Bruzenak
2008-08-25 20:41 ` Steve Grubb
2008-08-25 20:47 ` LC Bruzenak
2008-08-25 21:03 ` LC Bruzenak [this message]
2008-08-25 21:09 ` Steve Grubb
2008-08-25 23:41 ` LC Bruzenak
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=1219698212.7022.821.camel@homeserver \
--to=lenny@magitekltd.com \
--cc=linux-audit@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