public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: "Bill Tangren" <bjt@usno.navy.mil>
To: linux-audit@redhat.com
Subject: Re: more on limiting auditing of file access
Date: Mon, 5 Nov 2007 15:32:13 -0500 (EST)	[thread overview]
Message-ID: <33080.10.1.5.58.1194294733.squirrel@aa.usno.navy.mil> (raw)
In-Reply-To: <200711051508.05153.sgrubb@redhat.com>


On DATE, the author spaketh: Steve Grubb
> On Monday 05 November 2007 01:36:30 pm Bill Tangren wrote:
>> I have a rule that audits failed access to files:
>>
>> -a exit,always -S chmod -S lchown -S chown -F success=0
>>
>> I assume that this is the rule that is causing so many files accessed by
>> the web server to be logged. How can change this rule to exclude user
>> apache from tripping this rule?
>
> Fields (-F options) are "anded" to decide whether to trigger or not. So,
> you
> could use:
>
> -a exit,always -S chmod -S lchown -S chown -F success=0 -F uid!=apache
>
> But you could chose to limit by partition or exact error code, too. For
> example, you may not want the failures due to ENOENT (file doesn't exist).
> In
> that case, it would be:
>
> -a exit,always -S chmod -S lchown -S chown -F success=0 -F exit!=-2
>
> -Steve
>

Thanks, Steve. I'll try these out.

And sorry about the off-list post. Don't know why that happens sometimes,
and I seem to always forget to check.

Bill

-- 
Bill Tangren
U.S. Naval Observatory

      reply	other threads:[~2007-11-05 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05 18:36 more on limiting auditing of file access Bill Tangren
2007-11-05 20:08 ` Steve Grubb
2007-11-05 20:32   ` Bill Tangren [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=33080.10.1.5.58.1194294733.squirrel@aa.usno.navy.mil \
    --to=bjt@usno.navy.mil \
    --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