All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Gruhn <Dan.Gruhn@groupw.com>
To: linux-audit@redhat.com
Subject: Audit Prelude Logout Tracking
Date: Wed, 18 Feb 2009 16:58:36 -0500	[thread overview]
Message-ID: <499C848C.6020401@groupw.com> (raw)

I''m working on an X86_64  RHEL 5.2 system and for NISPOM Chapt. 8 I'm 
looking to modify the audisp-prelude plugin so that I can get logout 
events displayed.

I see the information in the audit.log as USER_END and have done a small 
mod in the handle_event routine in audisp-prelude.c so that it looks for 
AUDIT_USER_END but I've run across the following things:

1) sshd goes through a login/logout cycle ending in USER_END and all is 
good.
node=node01 type=USER_END msg=audit(1234979707.894:203): user pid=7422 
uid=0 auid=0 subj=system_u:system_r:unconfined_t:s0-s0:c0.c1023 
msg='PAM: session close acct="root" : exe="/usr/sbin/sshd" 
(hostname=master, addr=10.1.4.100, terminal=ssh res=success)'



2) gdm-binary goes through the same login/logout cycle, but on the 
USER_END audit message it is missing some information, in particular the 
source hostname:
node=master type=USER_END msg=audit(1234988646.589:364): user pid=6868 
uid=0 auid=0 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='PAM: 
session close acct="root" : exe="/usr/sbin/gdm-binary" (hostname=?, 
addr=?, terminal=:0 res=success)'

3) When crond runs, it goes through a similar cycle (but without the 
USER_LOGIN step) ending with USER_END
node=master type=USER_END msg=audit(1234989001.710:371): user pid=9517 
uid=0 auid=0 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='PAM: 
session close acct="root" : exe="/usr/sbin/crond" (hostname=?, addr=?, 
terminal=cron res=success)'

I want to ignore the crond operations and be able to fill in the 
information from gdm-binary.  Has any one done this prelude logout 
tracking before or have any ideas how I can proceed.

As always, a pointer to more information is quite acceptable.

Dan

             reply	other threads:[~2009-02-18 21:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18 21:58 Dan Gruhn [this message]
2009-02-18 22:44 ` Audit Prelude Logout Tracking LC Bruzenak
2009-02-18 23:25   ` LC Bruzenak
2009-02-19 14:26     ` Dan Gruhn
2009-02-19 14:36       ` Steve Grubb
2009-02-19 15:24         ` LC Bruzenak
2009-02-19 18:39           ` Steve Grubb
2009-02-19 19:49             ` LC Bruzenak
2009-02-19 14:45       ` LC Bruzenak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=499C848C.6020401@groupw.com \
    --to=dan.gruhn@groupw.com \
    --cc=linux-audit@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.