From mboxrd@z Thu Jan 1 00:00:00 1970 From: "John Calcote" Subject: content and format? Date: Thu, 14 Dec 2006 10:24:14 -0700 Message-ID: <4581264E.37FF.0081.0@novell.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=__Part8AAE43AE.0__=" Return-path: Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id kBEHOU2a014235 for ; Thu, 14 Dec 2006 12:24:30 -0500 Received: from sinclair.provo.novell.com (sinclair.provo.novell.com [137.65.248.137]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id kBEHOS7i021083 for ; Thu, 14 Dec 2006 12:24:28 -0500 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 --=__Part8AAE43AE.0__= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline So what's in the future for linux audit regarding content and format? My company's really interested in this aspect of audit in order to provide good analytical tools for audit logs. Anyone? ----- John Calcote (jcalcote@novell.com) Sr. Software Engineeer Novell, Inc. --=__Part8AAE43AE.0__= Content-Type: text/plain; name="John Calcote.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="John Calcote.vcf" BEGIN:VCARD VERSION:2.1 X-GWTYPE:USER FN:John Calcote TEL;WORK:1-801-861-7517 ORG:;Unified Identity System Eng TE TEL;PREF;FAX:801/861-2292 EMAIL;WORK;PREF;NGW:JCALCOTE@novell.com N:Calcote;John;;Sr. Software Engineer TITLE:Sr. Software Engineer ADR;DOM;WORK;PARCEL;POSTAL:;PRV-H-511;;Provo LABEL;DOM;WORK;PARCEL;POSTAL;ENCODING=3DQUOTED-PRINTABLE:John Calcote=3D0A= =3D PRV-H-511=3D0A=3D Provo END:VCARD --=__Part8AAE43AE.0__= Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --=__Part8AAE43AE.0__=--