From: Steve <m6x@ornl.gov>
To: Steve <mckinneysj@ornl.gov>, linux-audit@redhat.com
Subject: Re: Bypassing audit's file watches
Date: Mon, 10 Jul 2006 07:32:26 -0400 [thread overview]
Message-ID: <44B23ACA.10409@ornl.gov> (raw)
In-Reply-To: <20060708020002.GA5350@dill.zko.hp.com>
Amy Griffis wrote:
> Steve wrote: [Fri Jul 07 2006, 10:58:42AM EDT]
>> 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.
>
> Are you seeing the open and not the write, or no records at all?
> If you are missing events for open() calls, please let us know since
> that would be a bug (versus a lacking feature).
I am not seeing the open() or any other syscall records.
Steve
next prev parent reply other threads:[~2006-07-10 11:32 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
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 [this message]
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=44B23ACA.10409@ornl.gov \
--to=m6x@ornl.gov \
--cc=linux-audit@redhat.com \
--cc=mckinneysj@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