[bug-notifications] [openssh 0004494]: sshd shows wrong "last login" date/time

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4494 
====================================================================== 
Reported By:                helmped
Assigned To:                yann
====================================================================== 
Project:                    openssh
Issue ID:                   4494
Category:                   regular use
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
====================================================================== 
Date Submitted:             2010-07-20 15:45 CEST
Last Modified:              2011-09-20 12:54 CEST
====================================================================== 
Summary:                    sshd shows wrong "last login" date/time
Description: 
Login in on any host (SPARC/x86, latest CSWossh installed) via ssh shows
not the last session login date/time. Instead the actual login date/time is
displayed.

Using SUNs sshd the login date/time information is correct.

Regards

Helmut
====================================================================== 

---------------------------------------------------------------------- 
 (0009288) helmped (reporter) - 2011-09-20 12:54
 https://www.opencsw.org/mantis/view.php?id=4494#c9288 
---------------------------------------------------------------------- 
Hi,

thanks for reminding me ...

I think I was a little confused about my comments and your
answers/question
but testing again I see that your comments are correct - only
sun ssh update the wtmpx file. Since the non-interactive logins are
reported in /var/adm/messages these logins can also be tracked.
I only have to know not to forget this.

Today I installed the new openssh opencsw package and now the correct
"last login" time is shown - seems the problem is now fixed.

Best Regards