public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Pete Briggs <pbriggs@ll.mit.edu>
To: Steve Grubb <sgrubb@redhat.com>
Cc: "NENTWIG, CHRISTOPHER R." <cnentwig@ll.mit.edu>,
	linux-audit@redhat.com, "GIOVANNUCCI JR,
	ROBERT F." <bobg@ll.mit.edu>, "HEALEY-DYSZCZYK ,
	 PAMELA J." <pamela@ll.mit.edu>
Subject: Re: "Watch"ing a directory
Date: Wed, 22 Aug 2007 11:40:00 -0400	[thread overview]
Message-ID: <1187797200.3151.133.camel@prudence.llan.ll.mit.edu> (raw)
In-Reply-To: <200708221036.35928.sgrubb@redhat.com>

Once I tried something like touching a file, this worked as advertised,
I'm using kernel:

2.6.21-1.3194.fc7

on Fedora 7

Thanks again - Pete Briggs

On Wed, 2007-08-22 at 10:36 -0400, Steve Grubb wrote:
> 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 15:40 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
2007-08-22 15:40             ` Pete Briggs [this message]
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=1187797200.3151.133.camel@prudence.llan.ll.mit.edu \
    --to=pbriggs@ll.mit.edu \
    --cc=bobg@ll.mit.edu \
    --cc=cnentwig@ll.mit.edu \
    --cc=linux-audit@redhat.com \
    --cc=pamela@ll.mit.edu \
    --cc=sgrubb@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