From mboxrd@z Thu Jan 1 00:00:00 1970 From: LC Bruzenak Subject: audisp-prelude login question Date: Wed, 29 Oct 2008 21:28:18 -0500 Message-ID: <1225333698.9388.287.camel@homeserver> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m9U2T7u6030740 for ; Wed, 29 Oct 2008 22:29:07 -0400 Received: from mail.magitekltd.com (rrcs-24-242-137-197.sw.biz.rr.com [24.242.137.197]) by mx3.redhat.com (8.13.8/8.13.8) with ESMTP id m9U2SJei025868 for ; Wed, 29 Oct 2008 22:28:19 -0400 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 1KvNEz-0004YJ-Fa for linux-audit@redhat.com; Wed, 29 Oct 2008 21:26:29 -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 List-Id: linux-audit@redhat.com Steve, This is a follow-up to the question I sent you earlier. Thanks for the suggestions. It does appear that the xdm login is auditing just fine, however the audisp-prelude plugin appears to not send the events to the prelude server. I think this is the difference: When sent by gdm it is this: node=hugo type=USER_LOGIN msg=audit(10/29/2008 21:03:49.410:256209) : user pid=16890 uid=root auid=lenny subj=system_u:system_r:xdm_t:s0-s15:c0.c1023 msg='uid=lenny exe=/usr/libexec/gdm-session-worker (hostname=, addr=?, terminal=/dev/tty7 res=success)' When sent by xdm it is this: node=v1 type=LOGIN msg=audit(10/29/2008 21:19:35.287:30749) : login pid=29371 uid=root old auid=unset new auid=lenny old ses=4294967295 new ses=1646 Note that the types are different. So, is USER_LOGIN (above) = AUDIT_USER_LOGIN 1112 (from libaudit.h) ? If so, what is LOGIN? I guess I can go look at the code and find out...but I guess that one isn't being grabbed inside the audisp-prelude handle_event() routine. If this is the case either the sending code could be made to match (I guess pam isn't doing it the same way in each) or else the audisp-prelude could be changed to send this one too? Thx, LCB. -- LC (Lenny) Bruzenak lenny@magitekltd.com