similar to: [Bug 1732] New: Proper utmpx support for FreeBSD HEAD

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 openssh-1.2.1pre20 has been released at: http://violet.ibs.com.au/openssh/files/ This release integrates more of Andre Lucas' portability patch, Ben Taylor's utmpx patch and some cleanups and bugfixes of my own. The auth-passwd failures should be fixed, as should lastlog support on NetBSD. Since Andre Lucas' patch included platform

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 openssh-1.2.1pre20 has been released at: http://violet.ibs.com.au/openssh/files/ This release integrates more of Andre Lucas' portability patch, Ben Taylor's utmpx patch and some cleanups and bugfixes of my own. The auth-passwd failures should be fixed, as should lastlog support on NetBSD. Since Andre Lucas' patch included platform

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

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

Using the latest cvs sources, the compilation of ssh.c fails. The 'struct rlimit rlim;' line is being expanded by cpp into 'struct rlimit64 rlim;' and there is no struct rlimit64 defined. In order to get the struct rlimit64 to be included when the #include <sys/resource.h> is used, it appears to need the _LARGEFILE64_SOURCE symbol defined OR it needs the '#if

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

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

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.

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

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

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

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

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

On 10 Jan 2015, at 17:35, Dimitry Andric <dimitry at andric.com> wrote: > > It looks like the interpretation of what "__STDC_MB_MIGHT_NEQ_WC__" means differs between the llvm developers and the FreeBSD developers. I'm not sure what a good solution is. I've just read the relevant parts of the C11 spec, and it's not really clear to me what the 'basic

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

Hello, I just installed the above openssh onto a Sun Solaris 7 and Solaris 8 system. No problem with that. However, I now seem to get some rubbish processed when I login with slogin. An example: Last login: Tue Jun 13 12:31:27 2000 from jhorne.csd.plymo:tJ` ^[[?1;2c Telnet logs in okay, but just shows 'Last login...jhorne.csd.plymo'. This seems to get passed to the shell, which it of

The problem seems to be that if you #include <utmpx.h> without suitable -DPOSIX_SOMETHING magic, you get no struct utmpx (all that stuff is wrapped w/ "#ifdef _INCLUDE_XOPEN_SOURCE_EXTENDED"). I'm not sure how you all are handling such portability issues. Thx, Will ================== I configured with # ./configure --prefix=/.=our-deploy/openssh-1.2.2 --without-shadow