similar to: OpenSSH: Solaris login and utmpx

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

I was having problems getting the UseLogin option to work on Solaris. I would recieve this error: No utmpx entry. You must exec "login" from the lowest level "shell". This led me to believe that Solaris login wants a utmpx entry in order to function. I put together a patch that calls record_login on Solaris when using the system login. I also noticed that writing a wtmpx

Attached is the latest version of my UseLogin patch that makes "UseLogin true" work on Solaris and UNICOS. As usual, I have provided configure.in changes that set the appropriate defines for Solaris, but I have not provided the configure.in changes for UNICOS (since they would be incomplete, and Wendy is working on this). This version fixes a problem with the last-login time always

http://bugzilla.mindrot.org/show_bug.cgi?id=378 Summary: sshd does not update utmp/utmpx records correctly when "UseLogin" feature on Product: Portable OpenSSH Version: -current Platform: MIPS OS/Version: IRIX Status: NEW Severity: normal Priority: P2

http://bugzilla.mindrot.org/show_bug.cgi?id=378 drk at sgi.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary| sshd |sshd does not update |does not update utmp/utmpx |utmp/utmpx records correctly |records correctly when

it seems that --enable-utmpx and friends have the effect of disabling the corresponding feature (i.e., #define-ing DISABLE_UTMPX etc.), which leads to the (perhaps not so) obvious breakage of UseLogin on Solaris etc. For the less anal (or reformed anal) configure-r who leaves these unspecified, everything is OK i'd suggest changes to configure.in, but i'm blissfully ignorant of autoconf.

Hello Porters, I've finally (thanks to Wendy Palm of Cray) ported OpenSSH to Dynix v4.4.4. I had to make sure that "UseLogin" was set to "no" in the sshd_config file. Also, here are the old-style contextual diffs (obtained with 'diff -c' on the Dynix box) of the two files I had to change: *** configure Sat Jun 16 17:09:50 2001 --- configure.new Mon Oct 8

hello, I'm attempting to compile 2.9p1 on Solaris 2.6 with AFS support. I am not using Kerberos aside from AFS. The installation notes state that Kerberos IV is required by AFS. Since the Kerberos libraries and header files do not appear to be distributed with AFS, I downloaded and installed ftp://ftp.pdc.kth.se/pub/krb/src/krb4-1.0.8.tar.gz ./configure --sysconfdir=/etc/ssh

Hello OpenSSH hackers, The last couple of weeks I've been figuring out how hard it is to replace FreeBSD's <utmp.h> with <utmpx.h>. I don't think utmpx is perfect, but at least it's better than what we have now and at least it has gone through some form of standardisation. I noticed POSIX says the following [1]: | The <utmpx.h> header shall define the utmpx

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

https://bugzilla.mindrot.org/show_bug.cgi?id=1732 Summary: Proper utmpx support for FreeBSD HEAD Product: Portable OpenSSH Version: 5.4p1 Platform: Other OS/Version: FreeBSD Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: unassigned-bugs at mindrot.org ReportedBy: ed

https://bugzilla.mindrot.org/show_bug.cgi?id=378 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |djm at mindrot.org, |

http://bugzilla.mindrot.org/show_bug.cgi?id=960 Summary: Support needed for NetBSD utmpx field ut_ss Product: Portable OpenSSH Version: 3.9p1 Platform: All OS/Version: NetBSD Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org ReportedBy: eravin

In case it is any help, here is the patch against openssh-3.0.1p1 that corrects the problem with last reporting on Solaris that I sent to the list a week or so ago against 3.0p1. There was no conversation about this aside from Rip Loomis' comment about including it to support BSM auditing - does this present a problem for other OSes to include the ut_name field in the utmpx entry? Should this

https://bugzilla.mindrot.org/show_bug.cgi?id=378 --- Comment #3 from Darren Tucker <dtucker at zip.com.au> --- Comment on attachment 2590 --> https://bugzilla.mindrot.org/attachment.cgi?id=2590 skip record_login in privsep when UseLogin is active >+ if (!options.use_login) >+ return; >+ Err, that's going to skip the login recording when UseLogin is INactive. -- You

I cannot make openssh on Solaris. The 'make' fails on the first file. Here are the commands and the output. Essentially, I pre-built EGD, SSL, and ran: configure make make errors are listed at the bottom. Can anyone help me get this compiled on Solaris7? Steve sdn at sprintlabs.com ./configure --prefix=/common --sysconfdir=/etc/ssh --with-egd-pool=/common/bin/egd.pl loading cache

I've installed Sun's SUNWski package on Solaris 8 (32-bit) that provides a /dev/random interface. It appears to as cat'ing it gives me a bunch of well, random data. However, when I ran my configure, it gives me the WARNING.RND message to the effect that I'm using the built-in. I've seen allusions on this list to building openssl with to get random support, so I rebuilt it

Hi, I hope I'm not asking some FAQ, but I can't compile openssh-2.9p2 on maas34:openssh-2.9p2 {173} uname -a SunOS maas34 5.6 Generic_105181-23 sun4u sparc SUNW,Ultra-5_10 using: maas34:openssh-2.9p2 {174} gcc -v Reading specs from /opt/local/gcc-2.95.2/lib/gcc-lib/sparc-sun-solaris2.6/2.95.2/specs gcc version 2.95.2 19991024 (release) I get: maas34:openssh-2.9p2 {172}

Hi, I'm using the system accounting functionallity of Samba 2.2.6. Everything is working fine and dandy except that there is a lag between when a user logs out of a Windos 2000 Domain member, the 'who' command still lists the user as logged on for the next 20 - 30 seconds. Does anyone know what causes this? Can I increase the frequency of utmpx updates? Can someone point me to an

Hello all, The next version of FreeBSD will use utmpx for its user accounting database, as opposed to utmp which is used right now. Unfortunately wtmpx and lastlog handling isn't standardized at all, which is why we took the liberty to integrate all these databases into a compact API, where setutxdb() can be used to switch to a different database and getutxuser() to search for a USER_PROCESS