All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: pbriggs@ll.mit.edu
Cc: linux-audit@redhat.com
Subject: Re: "Watch"ing a directory
Date: Wed, 22 Aug 2007 10:36:34 -0400	[thread overview]
Message-ID: <200708221036.35928.sgrubb@redhat.com> (raw)
In-Reply-To: <1187792258.3151.108.camel@prudence.llan.ll.mit.edu>

On Wednesday 22 August 2007 10:17:37 Pete Briggs wrote:
> Is there any way to put a watch on a directory, 

Sort of...RHEL5.1 will have subtree auditing working in it. Al Viro also sent 
the patch upstream and should land in 2.6.23 or 24.

> so that an audit record will be generated if anyone cd's to that directory. 

Not for cd'ing into a directory. They have to attempt to read, write, change 
an attribute, or execute a file.

> I've tried things like:
>
> -w /etc/audit/ -k ACCESS_AUDIT

That is how you would watch a directory with current audit package and kernel 
with the subtree auditing patch.

> but the rule never seems to get invoked. I'm running FC7 with
> audit-1.5.3

They have to actually do something for it to trip...assuming you have a kernel 
that supports it.

-Steve

  reply	other threads:[~2007-08-22 14:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21 15:13 Auditing failed kill events Henning, Arthur C. (CSL)
2007-08-21 15:50 ` Steve Grubb
2007-08-21 17:50   ` Henning, Arthur C. (CSL)
2007-08-21 18:16     ` Steve Grubb
2007-08-21 21:19       ` Henning, Arthur C. (CSL)
2007-08-22 14:17         ` "Watch"ing a directory Pete Briggs
2007-08-22 14:36           ` Steve Grubb [this message]
2007-08-22 15:40             ` Pete Briggs
2007-08-22 16:03               ` Steve Grubb
2007-08-22 20:37             ` Wieprecht, Karen M.
2007-08-22 14:40           ` Sankarshan Mukhopadhyay
2007-08-22 14:59             ` Steve Grubb
2007-08-22 15:03               ` Eric Paris
2007-08-22 15:05               ` Ameel Kamboh
2007-08-22 16:09                 ` Steve Grubb
2007-08-22 20:16                   ` Ameel Kamboh

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=200708221036.35928.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=pbriggs@ll.mit.edu \
    /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.