From mboxrd@z Thu Jan 1 00:00:00 1970 From: LC Bruzenak Subject: user audits Date: Fri, 03 Dec 2010 09:40:37 -0600 Message-ID: <1291390837.2184.24.camel@lcb> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.redhat.com (ext-mx10.extmail.prod.ext.phx2.redhat.com [10.5.110.14]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id oB3Fen00009249 for ; Fri, 3 Dec 2010 10:40:49 -0500 Received: from mail.magitekltd.com (rrcs-24-242-137-197.sw.biz.rr.com [24.242.137.197]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id oB3FecBE014556 for ; Fri, 3 Dec 2010 10:40:38 -0500 Received: from [24.242.137.194] (helo=[192.168.30.40]) by mail.magitekltd.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1POXjk-0002A5-Ip for linux-audit@redhat.com; Fri, 03 Dec 2010 09:39:52 -0600 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 List-Id: linux-audit@redhat.com Steve, Would there be any issue with adding a couple new trusted_application event types? Would any kernel mods be needed to support this? The reason I ask is because I'd like to process some event types differently on the back end (the aggregator) and if I could easily identify those types it would make life easier. Some trusted_application events are for recording "bad" security issues, some for "good", etc. and I'd like to easily differentiate those. I can put something inside the event text but if possible would prefer a couple different types, like trusted_app1, trusted_app2, etc. Thx, LCB -- LC (Lenny) Bruzenak lenny@magitekltd.com