From mboxrd@z Thu Jan  1 00:00:00 1970
From: Linda Knippers <linda.knippers@hp.com>
Subject: Re: Not auditing dispatchers
Date: Fri, 06 Jun 2008 18:53:01 -0400
Message-ID: <4849BFCD.2080808@hp.com>
References: <48492BBC.40400@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <linux-audit-bounces@redhat.com>
In-Reply-To: <48492BBC.40400@redhat.com>
List-Unsubscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/linux-audit>
List-Post: <mailto:linux-audit@redhat.com>
List-Help: <mailto:linux-audit-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=subscribe>
Sender: linux-audit-bounces@redhat.com
Errors-To: linux-audit-bounces@redhat.com
To: Matthew Booth <mbooth@redhat.com>
Cc: Linux Audit <linux-audit@redhat.com>
List-Id: linux-audit@redhat.com

You could construct your audit rules dynamically so that they
exclude the dispatcher.  You'd have to know its pid and then have
a -F pid!= xxx option on your audit rules.  I haven't tried that
but it should work.  You'd have to re-do the rules if the dispatcher
was restarted so its kind of clunky.

I think the feature that LAuS had for letting trusted programs
enable/disable auditing of themselves was kind of handy.

-- ljk

Matthew Booth wrote:
> The kernel ignores auditable events from the audit daemon, but is there
> an 'approved' way to achieve the same for dispatchers? The problem is
> the same, in that you get an infinite loop if the dispatcher itself
> performs any action which generates an audit record.
> 
> Thanks,
> 
> Matt