From: LC Bruzenak <lenny@magitekltd.com>
To: Linux Audit <linux-audit@redhat.com>
Subject: Re: audisp-prelude event not propagated?
Date: Wed, 16 Sep 2009 22:13:36 -0500 [thread overview]
Message-ID: <1253157216.4713.168.camel@lcb> (raw)
In-Reply-To: <1253156405.4713.157.camel@lcb>
On Wed, 2009-09-16 at 22:00 -0500, LC Bruzenak wrote:
> 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
>
The detail in the IDS event generated locally on the collector isn't
complete. Under "Target" there is a "Target file current" block. The
"Name" value shows up as: "/" but the "Path" value is "/boot/".
The corresponding audit event is below.
node=audit type=PATH msg=audit(09/16/2009 20:26:54.945:271) : item=1
name=/boot/test inode=16 dev=08:01 mode=file,644 ouid=root ogid=root
rdev=00:00 obj=unconfined_u:object_r:boot_t:s0
node=audit type=PATH msg=audit(09/16/2009 20:26:54.945:271) : item=0
name=/boot/ inode=2 dev=08:01 mode=dir,755 ouid=root ogid=root
rdev=00:00 obj=system_u:object_r:boot_t:s0
node=audit type=CWD msg=audit(09/16/2009 20:26:54.945:271) : cwd=/root
node=audit type=SYSCALL msg=audit(09/16/2009 20:26:54.945:271) :
arch=x86_64 syscall=open success=yes exit=3 a0=7fffbe53d9c3 a1=941
a2=1b6 a3=386016d12c items=2 ppid=2275 pid=2448 auid=root uid=root
gid=root euid=root suid=root fsuid=root egid=root sgid=root fsgid=root
tty=pts0 ses=1 comm=touch exe=/bin/touch
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
key=ids-file-hi
Maybe the 2 "PATH" components confused the plugin code?
LCB.
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
next prev parent reply other threads:[~2009-09-17 3:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 3:00 audisp-prelude event not propagated? LC Bruzenak
2009-09-17 3:13 ` LC Bruzenak [this message]
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=1253157216.4713.168.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox