similar to: patch to add utmps support for HP-UX 11.23 and above

http://bugzilla.mindrot.org/show_bug.cgi?id=979 Summary: Openssh doesn't support UTMPS/BTMPS/WTMPS database Product: Portable OpenSSH Version: 3.9p1 Platform: Other OS/Version: HP-UX Status: NEW Severity: enhancement Priority: P5 Component: Miscellaneous AssignedTo: openssh-bugs at mindrot.org

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

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 it corrupts the /var/adm/wtmpx

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_write_entry()

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.sfu. Mon Jan 15

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. Next command I run from Solaris 8 console

Hi, Attached is a patch to 1.2.1pre18 that includes a number of portability changes, and more a more complete HPUX10.20 implementation. Thanks to Ben Taylor's utmpx patch, utmpx and wtmpx support are now in for HP, with a few caveats. It compiles cleanly on HPUX10.20 with gcc, cleanly on Linux, and with a few minor warnings on Solaris 2.6. Most compat changes are made via autoconf which

This is just portable todo list. From the sounds of it Markus has his own to do list. But can everyone review and let me know if there is anything missing from this list. (Note.. I'm not looking for 'SSH should support XYZ feature.' unless it's directly related to portability.) Or if there is anything on this list that has been completed. (Namely Tru64 SIA support?) Thanks.

Hi there, I'm using samba-2.2.2 under Solaris 8 and I've got the following problem! I have configured samba with "--with-utmp" and with "--with-quota" and everything works fine. But when look for the last users logged in, in the utmp-database there are only the first seven letters of the username, not eight that we use for usernames. Can you help me with this problem

I'm using openssh 2.5.2p2 on Solaris-x86 2.6. I ran into a couple problems when I set UseLogin to "yes": The big one seems to have been reported before: login refuses to run without a utmpx entry. This problem appears to have been caused by the changes in revision 1.24 of session.c. Before this revision, the record_login() function was always called, no matter how UseLogin was

sessreg is used by display managers such as xdm and gdm to record X sessions in utmp, wtmp, and lastlog files. This release attempts 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

Joao Carlos Mendes Luis <jonny@coe.ufrj.br> wrote: > I think it would be useful if samba had a utmp log interface. > I know that it's possible to see who is logged with smbstatus, but > sometimes a simple who(1) or w(1) is more efficient and ubiquitous. If you were to search for 'wtmp' in the 1997 archives (via the Samba web pages), you would find one interesting

Hi, A lot of the problems with openssh portability so far appear to be with the login record functionality, i.e. lastlog support, and variations on handling utmp vs. utmpx etc. Looking at for-profit SSH 1.2.27, login.c is rather embarassing spaghetti code, so laden with '#ifdef's it's almost impossible to read. OpenSSH's code isn't anything like that, but then it doesn't

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

I'm seeing a problem using OpenSSH v2.9.9p2 on solaris and the usage of the "last" command. The "last <username>" usage is displaying the sessions as still being logged on the server when it's really not. The "last" by itself shows correct information about the session. Sometimes using the "last <username>" syntax the session shows

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

Building OpenSSH 4.2p1 with the hpn11-none patch, HP-UX 11.23 64-bits ia64, using openssl-0.9.7g compiled from source. Using gcc 4.0.2 from the HP software depot, compilation is uneventful (but fast!) once configuration is set up, but make tests fail with Disconnected messages: Disconnected: bad packet length ... (varying) Write failed: Broken pipe ssh -2 failed with mac hmac-sja1 cipher

I am using the "UseLogin yes" configuration parameter to call the /usr/bin/login program on SGI Irix, (we are using Irix version 6.5.13). I do this because the SGI login program is AFS awhere and checks out a token for you and I do not want to compile the Kerberos version of sshd, (it is to messy for me to support). Everything seems to work fine accept the wtmp(x) and utmp(x) files do

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 Furry Fan.

Using UseLogin on a system that has to twiddle utmpx before calling login currently also twiddles wtmpx, and this causes problems on Solaris in the "last" log. Changing the source to avoid modifying wtmpx when also modifying utmpx fixes things up nicely: Index: loginrec.c --- loginrec.c 2001/05/08 20:33:06 1.33 +++ loginrec.c 2001/06/06 17:14:25 @@ -456,9 +456,10 @@ # endif # ifdef