public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: USER_LOGIN
Date: Mon, 19 Jul 2010 10:07:05 -0400	[thread overview]
Message-ID: <201007191007.05469.sgrubb@redhat.com> (raw)
In-Reply-To: <AANLkTimketCyWMyDsJdYFuCTBp_8F3Z4hNzbfn7vCoki@mail.gmail.com>

On Monday, July 19, 2010 09:33:11 am List Quest wrote:
> - Trying FTP Connect:
> 
> Following lines writing to audit.log
> type=USER_AUTH ...
> type=USER_ACCT ...
> (NO USER_LOGIN LINE?)
> 
> Wyh this?

No one patched the ftp deamon to send it. The USER_LOGIN event is sent by the 
daemon after authentication/authorization completes. This is to distinguish 
actual sessions from the pam events you noted which may not actually be 
associated with a login (e.g. - crond). Sshd, gdm, kdm, xdm, and login have 
all been patched to do this. I'm not entirely sure we considered ftp to be a 
shell giving free access to the system and that would be the most likely 
reason its not been patched.

-Steve

  reply	other threads:[~2010-07-19 14:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19 13:33 USER_LOGIN List Quest
2010-07-19 14:07 ` Steve Grubb [this message]
2010-07-20 11:58   ` USER_LOGIN List Quest

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=201007191007.05469.sgrubb@redhat.com \
    --to=sgrubb@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox