similar to: OpenSSH 2.3.0p1 on Solaris

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

We're trying to build OpenSSH 3.0.2p1 for Solaris 8 (among others) and are running into a problem with UseLogin and utmpx. If we set "UseLogin no" then we can login okay. finger or who won't find us, even with a TTY allocated altough "who /etc/wtmpx" will find us. But the real problem is if we set "UseLogin true" which we must do for BSM support on some

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

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 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

Back on April 4th I sent a patch that makes UseLogin work on Solaris. This change also made UseLogin work with Unicos (both of which require a valid utmpx entry before /usr/bin/login will run). I have not heard back from any of the ssh developers about this issue, and the current snapshot doesn't appear to deal with this problem at all. So, is there some issue here we still need to deal

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

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

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.

Greetings, In order to use solaris's BSM (Basic security module) also called c2 audit, which logs specific kernel calls depending on your audit_control, I would need to use login(1) to log users exec calls and whatnot because Portable OpenSSH does not have <bsm/audit.h> support, now that would mean I would have to enable Uselogin in sshd_config in order for that to work. I am running

Hello, I tried UseLogin, because ssh does not seem to propagate the tty controlling characters from the local to the remote tty and the login(1) on my system offers a config file to set them. Unfortunately, when using UseLogin, sshd does not run xauth. I can only guess that it does so, because it would have to drop privileges for doing so, but that makes UseLogin about useless. I am not

Compile openssh-3.8p1 with gcc and the following flags --prefix=/tmp/build/sshd --with-ssl-dir=/tmp/build/lib --with-utmpx, no PAM. Everything complies correctly, and I changed sshd_config to use "UseLogin yes" When my client connects (using the newer ssh client too), I do not get the message that my password will expire in xx days, but sshd shows that it is picking up that info (next

Hi all! I've searched all the maillists but can't find a solution. I have problems using the "UseLogin yes" parameter of sshd. When I enable the feature I got: <<No utmpx entry. You must exec "login" from the lowest level "shell".>> I need local login binary, because of enhances login policies, sshd is not able to handle. - OpenSSH-2.2.0p1 -

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, |

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 to all! I have problem with OpenSSH 1.2.1pre18 on Linux (kernel 2.2.13, distribution Slackware 4.0). When someone login using ssh, there is no way to see his presentance with some 'standard' tools (finger, who, w, users...). Of course, his proccesses are in ps, and so. I've tried to see /etc/utmp using vi, and there is some entry, but maybe invalid, or something. When I enable

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

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

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

BSD/OS 4.2 comes with OpenSSH 2.1.1p4, patched to support BSDI's authentication library. However, BSDI's patches have several problems: 1. They don't run the approval phase, so they can allow users to login who aren't supposed to be able to. 2. They don't patch configure to automatically detect the BSDI auth system, so they're not ready to use in a general portable