Bug 1150 - sshd records incorrect login times
Summary: sshd records incorrect login times
Status: CLOSED FIXED
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: sshd (show other bugs)
Version: 4.3p1
Hardware: Other Solaris
: P2 major
Assignee: Assigned to nobody
URL: http://marc.theaimsgroup.com/?l=opens...
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-04 10:24 AEDT by Darren Tucker
Modified: 2006-10-07 11:44 AEST (History)
0 users

See Also:

Attachments
config.log from Solaris 8 (sparc) system (546.99 KB, text/plain)
2006-02-04 10:49 AEDT, Bill Fischer 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darren Tucker 2006-02-04 10:24:47 AEDT 
From the description by Matt Goebel:

it appears that OpenSSH_4.3p1 on solaris creates 
bad wtmpx entries during login?

mgoebel   pts/5                         Wed Dec 31 19:00   still logged in

It is creating entries for Dec 31st 1969.
Comment 1 Bill Fischer 2006-02-04 10:49:29 AEDT 
Created attachment 1061 [details]
config.log from Solaris 8 (sparc) system
Comment 2 Tim Rice 2006-02-04 11:58:56 AEDT 
(In reply to comment #0)
> From the description by Matt Goebel:
> 
> it appears that OpenSSH_4.3p1 on solaris creates 
> bad wtmpx entries during login?
> 
> mgoebel   pts/5                         Wed Dec 31 19:00   still logged in
> 
> It is creating entries for Dec 31st 1969.
> 

That is what would show up prior to the configure patch posted to the list.
I'm not able to duplicate that problem on my Solaris 8 box when building 
4.3p1 with patched configure.

The patch can be found at
http://marc.theaimsgroup.com/?l=openssh-unix-dev&m=113892892008957
or
http://www.zip.com.au/~dtucker/openssh/4.3p1-configure.patch
Comment 3 Damien Miller 2006-02-12 12:31:11 AEDT 
This should be fixed in 4.3p2 which has just been released. Could you please retest with this version?
Comment 4 Darren Tucker 2006-02-15 07:30:31 AEDT 
I checked with the original reporters and got confirmation that it was fixed from 2 out of 3 (no response from the third).
Comment 5 Darren Tucker 2006-10-07 11:44:21 AEST 
Change all RESOLVED bug to CLOSED with the exception of the ones fixed post-4.4.