From: "Timothy R. Chavez" <tinytim@us.ibm.com>
To: Amy Griffis <amy.griffis@hp.com>
Cc: linux-audit@redhat.com
Subject: Re: Bypassing audit's file watches
Date: Mon, 10 Jul 2006 10:16:23 -0500 [thread overview]
Message-ID: <1152544584.13544.11.camel@localhost.localdomain> (raw)
In-Reply-To: <20060708020002.GA5350@dill.zko.hp.com>
On Fri, 2006-07-07 at 22:00 -0400, Amy Griffis wrote:
<snip>
>
> As Tim mentioned, the idea is that to determine if a file is modified,
> you would filter for open() calls with either the O_RDWR or O_WRONLY
> flag. This is pretty unwieldy with the current feature set since you
> would need a separate rule for every possible combination of flags
> that includes O_RDWR or O_WRONLY. I really think we need to enhance
> the filtering options available for open() calls, since trying to
> audit the actual modifications is much more difficult.
>
> If you are missing events for open() calls, please let us know since
> that would be a bug (versus a lacking feature).
>
> Thanks for testing.
>
> Amy
>
I think this is a bug. We see audit records for a failed attempt at
writing a file (e.g. chmod -w foo, echo "bar" > foo) via redirection,
but not otherwise.
-tim
prev parent reply other threads:[~2006-07-10 15:16 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
2006-07-10 22:31 ` Amy Griffis
2006-07-11 15:07 ` Michael C Thompson
2006-07-10 15:16 ` Timothy R. Chavez [this message]
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=1152544584.13544.11.camel@localhost.localdomain \
--to=tinytim@us.ibm.com \
--cc=amy.griffis@hp.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