From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Booth Subject: Running auditd from inittab Date: Fri, 02 Feb 2007 13:02:52 +0000 Message-ID: <1170421372.6772.22.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1769543399==" Return-path: Received: from [192.168.250.101] (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.surrey.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id l12JpA4f024524 for ; Fri, 2 Feb 2007 19:51:12 GMT List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: linux-audit@redhat.com List-Id: linux-audit@redhat.com --===============1769543399== Content-Type: multipart/alternative; boundary="=-676K75aOBXsYi0peTbCE" --=-676K75aOBXsYi0peTbCE Content-Type: text/plain Content-Transfer-Encoding: 7bit I was testing various failures of auditd, and amongst them I tested kill -SEGV and kill -KILL. I noticed that neither of these generate any audit event or log activity. It occurs to me that this could be worked around, and at the same time you could provide some additional level of reliability, if auditd could be run from inittab. Unfortunately, the only option to auditd seems to be -f, and this prevents it from logging in the normal manner. Are there any other options which might achieve this? If not, is this a reasonable feature request? Thanks, Matt -- Red Hat, Global Professional Services M: +44 (0)7977 267231 GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490 --=-676K75aOBXsYi0peTbCE Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit I was testing various failures of auditd, and amongst them I tested kill -SEGV and kill -KILL. I noticed that neither of these generate any audit event or log activity. It occurs to me that this could be worked around, and at the same time you could provide some additional level of reliability, if auditd could be run from inittab. Unfortunately, the only option to auditd seems to be -f, and this prevents it from logging in the normal manner.

Are there any other options which might achieve this? If not, is this a reasonable feature request?

Thanks,

Matt
-- 
Red Hat, Global Professional Services

M:       +44 (0)7977 267231
GPG ID:  D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490
--=-676K75aOBXsYi0peTbCE-- --===============1769543399== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============1769543399==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Running auditd from inittab Date: Fri, 2 Feb 2007 15:24:38 -0500 Message-ID: <200702021524.38799.sgrubb@redhat.com> References: <1170421372.6772.22.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1170421372.6772.22.camel@localhost.localdomain> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Friday 02 February 2007 08:02, Matthew Booth wrote: > I was testing various failures of auditd, and amongst them I tested kill > -SEGV and kill -KILL. I noticed that neither of these generate any audit > event or log activity. KILL is uncatchable and SEGV would mean that the audit daemon is about to die, so no writing would be possible. > It occurs to me that this could be worked around, and at the same time you > could provide some additional level of reliability, if auditd could be run > from inittab. It was never intended to be run from that. > Unfortunately, the only option to auditd seems to be -f, and this prevents > it from logging in the normal manner. -f is for foreground debug. > Are there any other options which might achieve this? No. > If not, is this a reasonable feature request? I'm not sure. There are the issues of how to get rules loaded and logging partition availability. -Steve