All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Excluding stat syscall logging for specific path
Date: Fri, 29 Apr 2016 14:00:51 -0400	[thread overview]
Message-ID: <1734746.Y1sbE4bZ3d@x2> (raw)
In-Reply-To: <5723A04A.6080208@gmail.com>

On Friday, April 29, 2016 08:56:26 PM Vincas Dargis wrote:
> Hi,
> 
> When playing/learning with auditd, I wanted to log events when apache fails
> to access file.
> 
> Here's the rules I used in Debian Wheezy (same on Jessie and and current
> latest Testing):
> 
> -a exit,never -F arch=b64 -S stat -F path=/var/www/server-status -k web
> -a exit,always -F arch=b64 -S stat -F uid=www-data -F success=0 -k web
> 
> /var/www/server-status file is non-existant,

Is it a symlink? If it really doesn't exist, then there is no inode to match 
against.


> it's just alias for accessing
> mod_status information ( http://.../server-status path is accessed by munin
> regularly) so I wanted to minimise noise by that exit,never rule.
> 
> But I can't get it work.

What kernel are you using?

-Steve

> I have more in-depth post in Debian forums [1] if that helps, but in short,
> should this work in general?
> 
> Thanks!
> 
> [1] http://forums.debian.net/viewtopic.php?f=5&t=128092
> 
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit

  reply	other threads:[~2016-04-29 18:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29 17:56 Excluding stat syscall logging for specific path Vincas Dargis
2016-04-29 18:00 ` Steve Grubb [this message]
2016-04-29 18:16   ` Vincas Dargis
2016-04-29 18:48     ` Steve Grubb
2016-04-29 19:05       ` Vincas Dargis

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=1734746.Y1sbE4bZ3d@x2 \
    --to=sgrubb@redhat.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 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.