From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dustin Kirkland" Subject: Re: [PATCH] Rework of IPC auditing Date: Fri, 31 Mar 2006 15:13:44 -0600 Message-ID: References: <1142018719.13416.91.camel@kirkland1.austin.ibm.com> <200603311424.44064.sgrubb@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.12.11.20060308/8.11.6) with ESMTP id k2VLDtg6002457 for ; Fri, 31 Mar 2006 16:13:55 -0500 Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.194]) by mx3.redhat.com (8.13.1/8.13.1) with ESMTP id k2VLDiTG007360 for ; Fri, 31 Mar 2006 16:13:49 -0500 Received: by xproxy.gmail.com with SMTP id h30so884495wxd for ; Fri, 31 Mar 2006 13:13:44 -0800 (PST) In-Reply-To: <200603311424.44064.sgrubb@redhat.com> 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: Steve Grubb Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com On 3/31/06, Steve Grubb wrote: > On Friday 10 March 2006 14:25, Dustin Kirkland wrote: > > 2) Support for an AUDIT_IPC_NEW_PERM audit message type. This allows > > for separate auxiliary audit records for normal operations on an IPC > > object and permissions changes. Note that the same struct > > audit_aux_data_ipcctl is used and populated, however there are separa= te > > audit_log_format statements based on the type of the message. > > Can we have another name for this record type? I don't want us to get i= n the > habit of adding "new" to the record type name. Is there something that = better > describes its purpose? I know we discussed on IRC, but for everyone's benefit, we're going to call this record type AUDIT_IPC_SET_PERM and the function audit_ipc_set_perm(), as it's called in each of the IPC_SET operations on the ipc objects. :-Dustin