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
[EMAIL PROTECTED]

--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit

Reply via email to