similar to: WARNING: OpenSSH BREAKS Solaris utmp!!

Hello I have problem with OpenSSH 2.1.1p1 on libc5 system (Slackware 4). I'm not sure if I had those problems with 1.2.x version of OpenSSH (on the same system), but I don't think so. When someone ends ssh session (logout, or something) utmp entry for that user doesn't get erased from UTMP file. In 'finger' I can see a lot of multiplicied users that are not actually logged

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

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

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

here are patches to compile portable openssh 2.1.1p2 on netbsd, and some other platforms I suppose. itojun -------------- next part -------------- $NetBSD: patch-aa,v 1.8 2000/07/02 22:07:56 itojun Exp $ --- configure.in.orig Sat Jul 1 15:52:55 2000 +++ configure.in Mon Jul 3 06:49:00 2000 @@ -647,2 +647,6 @@ +OSSH_CHECK_HEADER_FOR_FIELD(ut_name, utmp.h, HAVE_NAME_IN_UTMP)

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

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

This is to announce the availability of portable OpenSSH-2.1.0p2. This is a bug-fix release, addressing the following issues: - X authentication works again (thanks to Markus Friedl) - Don't touch utmp if utmpx is in use - Fix SIGCHLD problems on AIX and HPUX (Thanks to Tom Bertelson) - HPUX compile fixes (Thanks to Lutz Jaenicke) - Accept an empty shell in /etc/passwd - SunOS4 compile fixes.

This is to announce the availability of portable OpenSSH-2.1.0p2. This is a bug-fix release, addressing the following issues: - X authentication works again (thanks to Markus Friedl) - Don't touch utmp if utmpx is in use - Fix SIGCHLD problems on AIX and HPUX (Thanks to Tom Bertelson) - HPUX compile fixes (Thanks to Lutz Jaenicke) - Accept an empty shell in /etc/passwd - SunOS4 compile fixes.

loginrec.c:794 /* ut_syslen is the length of the utx_host string */ utx->ut_syslen = MIN(strlen(li->hostname), sizeof(utx->ut_host)); But utmpx.h (on Solaris) says: short ut_syslen; /* significant length of ut_host */ /* including terminating null */ So shouldn't the code above add +1 in the strlen

Today I installed OpenSSH-2.1.0 together with zlib-1.1.3 and OpenSSL-0.9.5a on Solaris 7 on an Ultra box. There appears to be something odd with the utmp stuff... if I just do a normal configure, utmp logging works fine, but 'w' will give me this: 10:03pm up 13 day(s), 21:42, 3 users, load average: 0.04, 0.07, 0.10 User tty login@ idle JCPU PCPU what wyodlows

A few days ago I installed OpenSSH-2.1.0 together with zlib-1.1.3 and OpenSSL-0.9.5a on Solaris 7 on an Ultra box. There appears to be something odd with the utmp stuff... if I just do a normal configure, utmp logging works fine, but 'w' will give me this: 10:03pm up 13 day(s), 21:42, 3 users, load average: 0.04, 0.07, 0.10 User tty login@ idle JCPU PCPU what

I tried configuring Samba 2.0.7pre4 on a OSF1 machine (actually a DEC Alpha running Digital Unix 4.0d) with --with-utmp. The autoconf system sets the variable HAVE_UTMPX_H The linking of smbd aborts with the message ---------------------------------------------------------- ld: Unresolved: getutmpx utmpxname updwtmpx *** Exit 1 ---------------------------------------------------------- If I

https://bugzilla.mindrot.org/show_bug.cgi?id=2111 Bug ID: 2111 Summary: Android does not properly implement utmp or wtmp. Product: Portable OpenSSH Version: 6.2p1 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 Component: Build system Assignee: unassigned-bugs

Follow-on to Charles Levert's <charles at comm.polymtl.ca> work on utmp_write_direct. Fixed: -- At logout, the utmp entry is cleared. Tested on SunOS 4.1.4. The code I added to loginrec.c is restricted to SUNOS4 pending QA testing on other platforms. This patch incorporates the work done by Charles Levert on 7/25/2000 00:43:22. (Do any of us sleep at

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

Hi, plese have you some idea for this problem? thanks, Lukas -- ---------- Forwarded message ---------- Date: Wed, 30 Sep 2009 23:09:59 +0200 (CEST) From: extmaillist at linuxbox.cz To: pilsl at goldfisch.at, Volker.Lendecke at SerNet.DE Cc: samba at lists.samba.org X-Spam-Score: -1.0 (), 4 required Subject: Re: [Samba] user cannot logon to domain although log says "auth

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

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

I run Samba 2.2.2 on any of there vendors/osversions/filesystems: o Solaris 8 / ufs o Tru64 Unix V5.0A / advfs o RedHat 7.1 / Kernel 2.4.2 / ext2fs all these are capable of handling large files (files with a 64-bit-offset larger than 4GB). At configure time, samba selects the proper compile flags (-D_LARGEFILE_SOURCE, -D_FILE_OFFSET_BITS=64) for use with large files. The problem: When I