public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Laurent Bigonville <bigon@debian.org>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: aulast only displaying reboot pseudo-users
Date: Thu, 5 Jun 2014 19:34:04 +0200	[thread overview]
Message-ID: <20140605193404.079be96c@fornost.bigon.be> (raw)
In-Reply-To: <1487476.CjeIAT3yaP@x2>

Le Wed, 04 Jun 2014 19:04:52 -0400,
Steve Grubb <sgrubb@redhat.com> a écrit :

> On Thursday, June 05, 2014 12:42:39 AM Laurent Bigonville wrote:
> > Le Wed, 04 Jun 2014 18:23:29 -0400,
> > 
> > Steve Grubb <sgrubb@redhat.com> a écrit :
> > > On Thursday, June 05, 2014 12:04:05 AM Laurent Bigonville wrote:
> > > > On my machine with audit 2.3.6 the following call to aulast is
> > > > only displaying the "reboot" pseudo-users and not the actual
> > > > logins:
> > > > 
> > > > ausearch --start this-month --raw | aulast --stdin
> > > > 
> > > > Passing the "--bad" option to aulast, seems to correctly return
> > > > the failed login attempt.
> > > > 
> > > > Also, adding the login name to the aulast command doesn't seems
> > > > to work at all even with the --bad option.
> > > > 
> > > > OTOH, the aulastlog command seems to work as expected.
> > > > 
> > > > An idea?
> > >  
> > >  Would this happen to be a system with a recent GDM and systemd?
> > > If
> > > 
> > > so, they are known to be messing up the audit trail. I am trying
> > > to write a system validation test suite to spot issues like this.
> > > If you look at gdm, its sending duplicate events. Systemd events
> > > don't make it to audit all the time. Its a mess on the desktop
> > > right now.
> > 
> > Yes indeed I'm running gdm 3.12 and systemd 208.
> > 
> > But I'm not seeing anything in aulast output when I'm login in on a
> > tty.
> > 
> > ausearch is however giving me this:
> > 
> > bigon@fornost:~$ sudo ausearch -m ALL -ts 00:35|grep test
> > type=USER_AUTH msg=audit(1401921359.577:1394): pid=15760 uid=0
> > auid=4294967295 ses=4294967295
> > subj=system_u:system_r:local_login_t:s0-s0:c0.c1023
> > msg='op=PAM:authentication acct="test" exe="/bin/login" hostname=?
> > addr=? terminal=/dev/tty1 res=success' 
> > type=USER_ACCT msg=audit(1401921359.577:1395): pid=15760 uid=0
> > auid=4294967295 ses=4294967295
> > subj=system_u:system_r:local_login_t:s0- s0:c0.c1023
> > msg='op=PAM:accounting acct="test" exe="/bin/login" hostname=?
> > addr=?> terminal=/dev/tty1 res=success'
> 
> You are missing a type=LOGIN event right here. If you do a "cat 
> /proc/self/loginuid" and its set to something besides -1, we have a
> kernel bug.
> 


Actually, my grepping was wrong, I'm seeing this the following line too:

type=LOGIN msg=audit(1401921359.597:1397): pid=15760 uid=0 old-auid=4294967295 new-auid=1002 old-ses=4294967295 new-ses=66 res=1

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

  reply	other threads:[~2014-06-05 17:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 22:04 aulast only displaying reboot pseudo-users Laurent Bigonville
2014-06-04 22:23 ` Steve Grubb
2014-06-04 22:42   ` Laurent Bigonville
2014-06-04 23:04     ` Steve Grubb
2014-06-05 17:34       ` Laurent Bigonville [this message]
2014-06-14 11:53         ` Laurent Bigonville
2014-06-16 21:20           ` Eric Paris
2014-06-16 21:24             ` Eric Paris
2014-06-16 21:28               ` Eric Paris
2014-06-17 13:29             ` Steve Grubb
2014-06-17 14:09               ` Laurent Bigonville
2014-06-17 14:31                 ` Eric Paris
2014-06-17 14:55                   ` Richard Guy Briggs
2014-06-17 15:04                     ` Steve Grubb
2014-06-17 14:56                   ` Steve Grubb
2014-06-17 15:15                     ` Richard Guy Briggs
2014-06-17 15:26                     ` Eric Paris
2014-06-17 16:30                       ` Steve Grubb

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=20140605193404.079be96c@fornost.bigon.be \
    --to=bigon@debian.org \
    --cc=linux-audit@redhat.com \
    --cc=sgrubb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox