From: "Timothy R. Chavez" <tinytim@us.ibm.com>
To: Steve <m6x@ornl.gov>
Cc: linux-audit@redhat.com
Subject: Re: Bypassing audit's file watches
Date: Fri, 07 Jul 2006 10:59:12 -0500 [thread overview]
Message-ID: <1152287952.21687.0.camel@localhost.localdomain> (raw)
In-Reply-To: <44AE76A2.9050205@ornl.gov>
On Fri, 2006-07-07 at 10:58 -0400, Steve wrote:
> I have found that I can modify files that are being watched and audit
> not catch it (ie. no events are dispatched). When monitoring a file for
> all system calls, I can:
>
> echo "" > /file/to/watch
>
> or
>
> cat some_file > /file/to/watch
>
> without generating audit events. I assume this has to do with how the
> kernel handles re-direction. Is it possible to catch these modifications?
>
> Thanks,
> Steve
What are your rules? You should catch these on open()
of /file/to/watch, right?
-tim
next prev parent reply other threads:[~2006-07-07 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 14:58 Bypassing audit's file watches Steve
2006-07-07 15:59 ` Timothy R. Chavez [this message]
2006-07-07 16:08 ` Michael C Thompson
2006-07-07 16:20 ` Michael C Thompson
2006-07-08 2:00 ` Amy Griffis
2006-07-10 11:32 ` Steve
2006-07-10 22:31 ` Amy Griffis
2006-07-11 15:07 ` Michael C Thompson
2006-07-10 15:16 ` Timothy R. Chavez
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=1152287952.21687.0.camel@localhost.localdomain \
--to=tinytim@us.ibm.com \
--cc=linux-audit@redhat.com \
--cc=m6x@ornl.gov \
/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