search for: wtmpx

Hi, I just installed OpenSSH 4.3p1 on our Solaris 8 machines and 'last' now shows wtmpx entries for ssh logins like zierke pts/4 Thu Jan 1 01:00 still logged in zierke pts/3 Thu Jan 1 01:00 - 10:56 (13183+09: instead of e.g. zierke pts/3 rzdspc10.informa Sat Feb 4 10:54 - 10:54 (00:00) zierke pts/2 rzds...

Hi, Solaris (tested with 2.6) needs a username in the logout record in the wtmpx file. Currently openssh (version 2.3.0p1) leaves the username (utmpx.ut_user) empty in logout records, which leads to conflicting results from the last command. Example: # last -5 siegert siegert pts/186 stikine.ucs.sfu. Mon Jan 15 14:26 still logged in siegert pts/105 stikine.ucs....

Hello When I was using OpenSSH-2.9p2 in Solaris 8 sparcv9 (64bit) environment, I found some trouble that wtmpx has broken. The size of utmpx structure object becomes larger than 32 bit environment in sparcv9 environment.Therefore, instead of using utmpx structure object, using futmpx structure object is better. In sparcv9 environment, futmpx structure object is used instead of utmpx structure object....

It appears to be a pervasive assumption in the Portable OpenSSH code that wtmp and wtmpx records for the end of a session do not need to include the user name or hostname. Unfortunately Solaris appears not to go along with that assumption; the Solaris "last" command shows all login sessions initiated by OpenSSH as never terminating, or sometimes terminating with the user'...

http://bugzilla.mindrot.org/show_bug.cgi?id=348 Summary: infinite loop scanning wtmpx Product: Portable OpenSSH Version: -current Platform: Other OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: rodney at bo...

http://bugzilla.mindrot.org/show_bug.cgi?id=464 Summary: sshd seems to corrupt the wtmpx Product: Portable OpenSSH Version: 3.5p1 Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: minor Priority: P4 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: pas50 a...

On SCO 5.0.7 and openssh 3.8.1p1, two entries are written to /etc/wtmp and /etc/wtmpx each time a user logs in via ssh. This can be demonstrated using the last(C) command. Any user connected via ssh will have two identical login and logout entries. On SCO, login_write() in loginrec.c calls both wtmp_write_entry() and wtmpx_write_entry() (USE_WTMP and USE_WTMPX are defined). wtmp_...

...------ I spent some time looking into this. Initially I did see that last was reporting users still logged in that had logged out of their ssh connection. I noticed logintest showed everything working as expected. Now I can not duplicate the problem. I didn't change any code but I did zero out wtmpx during my tests. Now I can etheir log in using rlogin or ssh and last shows the correct information after logout. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=464 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |793 nThis| | ------- You are receiving this mail because: ------- You are the assignee for the

I installed 2.5.1p2 on an irix system and noticed that if a user logged in typed "logname" it was providing the wrong username. File creations were correct, "w" produces the correct output....so something is funky in p2 that wasn't there in p1.

http://bugzilla.mindrot.org/show_bug.cgi?id=348 tim at multitalents.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From tim at multitalents.net 2002-07-15

http://bugzilla.mindrot.org/show_bug.cgi?id=464 pere at hungry.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pere at hungry.com ------- Additional Comments From pere at hungry.com 2003-04-03 03:03 ------- I see the same problem on IA64 HP/UX

Problem: 'last' output is incorrect, /var/adm/wtmpx is corrupted. Example: foster pts/1 Wed Dec 31 16:00 still logged in foster pts/3 dim Thu Aug 1 14:34 still logged in Solution: (workaround) This turned out to be an OpenSSH problem! If OpenSSH (only tested versions 3.4p1 and 3.5p1) is compiled 64-bit...

...tempts to clean up some inconsistencies around the handling of the various files. Long long ago, Unix systems had a utmp file to record who was currently logged in, and a wtmp file to record login history. Long ago, extended versions of the files & APIs for them were standardized as utmpx and wtmpx. sessreg attempted to deal with all of the variants, including several other BSD vs. SysV differences beyond those listed above. Previously, sessreg 1.0.x would check for both the original and extended API's. If the extended API's were available, sessreg would compile in support for utmp...

http://bugzilla.mindrot.org/show_bug.cgi?id=464 ------- Additional Comments From pas50 at cam.ac.uk 2003-01-09 02:11 ------- This is apparently a bug with compiling in 64 bit. David foster saw this. http://www.sunmanagers.org/pipermail/summaries/2002-October/004018.html ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

...ng terminated but the total logged in time is hours off. The console logins are not showing this behavior so Sun Support has been difficult to get answers on the differences why I'm seeing this strange behavior. Sun Support had me apply latest "last" patches and start a new /var/adm/wtmpx file. I'm not understanding the tie in between Solaris OS usage of the wtmpx file and OpenSSH. I was using OpenSSH v2.5.2p2. After upgrading and using the pam module I'm still seeing this problem. Can some else using Solairs verify this strange behavior or verify it's a possible...

Hi, I've installed openssh-2.1.0p2 on a Solaris 8 host (SPARC). The sshd corrupts utmpx/wtmpx when a client connects to this machine. Observable error: $ who who: Error --- entry has ut_type of 28265 when maximum is 9 It can be repeated and is attributable to the login done by sshd. Now, Solaris has only utmpx/wtmpx and not the old utmp/wtmp. It get's worse as more logins take place...

Howdy, Not sure, but 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. Thanks, Matt -- Matthew Goebel : goebel at emunix.emich.edu : Unix Jockey @ EMU : Hail Eris Neo-Student, Net Lurker, Donut consumer, and procrastinating...

...RSA, RSA2, DSA, etc and suggestions on when it would be best to use them. - Create a Documentation/ directory? Clean up configure/makefiles: - Clean up configure.in - There are a few double #defined variables left to do. HAVE_LOGIN is one of them. Consider NOT looking for information in wtmpx or utmpx or any of that stuff if it's not detected from the start - Replace the whole u_intXX_t evilness in acconfig.h with something better??? - Move all "openbsd-compat" files to it's own directory. Consider doing the same with libssh. I don't think we need to split ssh,...

I have some troubles with subj and proper utmpx/wtmpx functionality. After successfull ssh connect to Solaris 8 box, I run #w 11:59am up 13:45, 1 user, load average: 0.00, 0.01, 0.02 User tty login@ idle JCPU PCPU what root console 11:43am 9 bash # Record about my pts/1 login is absent....