All of lore.kernel.org
 help / color / mirror / Atom feed
From: LC Bruzenak <lenny@magitekltd.com>
To: Linux Audit <linux-audit@redhat.com>
Subject: audisp-prelude event not propagated?
Date: Wed, 16 Sep 2009 22:00:05 -0500	[thread overview]
Message-ID: <1253156405.4713.157.camel@lcb> (raw)

I have 2 machines: one collector and one sender.
I added a watched file key with the ids keyword on the sender machine.

Other IDS events (login, AVCs, etc.) propagate from the sender to the
collector, so I am sure they are registered correctly
(prelude-manager->prelude-manager). Watched file IDS events do not get
to the collector.

I have the same rule on the collector machine and verified it generated
the prelude "Watched File" event when I touched a file watched with the
key: 
[root@audit ~]# auditctl -l | grep ids
LIST_RULES: exit,always watch=/boot/test perm=wa key=ids-file-hi

Is this a prelude issue or an audit issue?

Thx,
LCB.

audit-1.7.13-1.fc10
prelude-manager-0.9.14.2-2.fc10.x86_64

-- 
LC (Lenny) Bruzenak
lenny@magitekltd.com

             reply	other threads:[~2009-09-17  3:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17  3:00 LC Bruzenak [this message]
2009-09-17  3:13 ` audisp-prelude event not propagated? LC Bruzenak
2009-09-17 16:24   ` LC Bruzenak
2009-09-17 17:15     ` 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=1253156405.4713.157.camel@lcb \
    --to=lenny@magitekltd.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.