All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Viro <aviro@redhat.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: Taylor_Tad@emc.com, linux-audit@redhat.com
Subject: Re: Question about setting watches in auto-mounted directories in RHEL 5.2
Date: Sun, 30 Nov 2008 10:11:10 -0500	[thread overview]
Message-ID: <20081130151040.GC14693@file.rdu.redhat.com> (raw)
In-Reply-To: <200811300915.52390.sgrubb@redhat.com>

On Sun, Nov 30, 2008 at 09:15:52AM -0500, Steve Grubb wrote:
> On Friday 21 November 2008 11:59:46 Taylor_Tad@emc.com wrote:
> > I'd like to set a file system watch so that any activity in an
> > auto-mounted directory is audited.
> 
> You can't at this point in time. When the rule is loaded, it needs to resolve 
> the path down to a device and inode. If the file system is not mounted, it 
> cannot do this and the rule is rejected.
> 
> 
> > It looks like just setting a watchon a parent directory isn't sufficient.  For
> > example, if I have directory path  /dir1/dir2 and auto-mount something at
> > /dir1/dir2/mount-dir, setting a file system watch on /dir1/dir2 doesn't
> > detect activity in the auto-mounted subtree.
> 
> True.
> 
> > Looking at the auditctl man page, it looks like I'd have to issue a command
> > like "/sbin/auditctl -q /dir1/dir2/mount-dir,/dir1/dir2" to tell the kernel
> > to watch the newly mounted file system as well. 
> 
> Yes.
> 
> 
> > Unfortunately, auto-mounts are, well, automatic, so there's no one to issue
> > that command.

You do realize that they are, in the end, done from userland?  Which is
the natural place to do that...

  reply	other threads:[~2008-11-30 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 16:59 Question about setting watches in auto-mounted directories in RHEL 5.2 Taylor_Tad
2008-11-30 14:15 ` Steve Grubb
2008-11-30 15:11   ` Alexander Viro [this message]
2008-11-30 15:47     ` Steve Grubb
2008-11-30 17:17       ` Alexander Viro

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=20081130151040.GC14693@file.rdu.redhat.com \
    --to=aviro@redhat.com \
    --cc=Taylor_Tad@emc.com \
    --cc=linux-audit@redhat.com \
    --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 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.