similar to: utmp update for bsd systems

re i have posted this before but received no response... is there anybod reading on this address? cu ----- Forwarded message (env-from mickey) ----- re this is a patch against samba-2.2.12p0 and adds support for updating utmp on bsds. code similarly ripped from openbsd's ftpd (; cu -- paranoic mickey (my employers have changed but, the name has remained) --- utmp.c Thu Aug 12

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

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

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=84 Summary: last command provides incorrect information on Solaris 8 Product: Portable OpenSSH Version: -current Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org

I have put together a simple set of diffs that corrects the problem described by Steven Fishback <sfishback at interpath.net> on 10-30 on this list regarding incorrect information reported by last on Solaris. The patches merely pass along the username in the utmpx record for a logout. Is there any reason why this would be a problem with other OSes? If not, maybe this could be rolled into the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have just uploaded 1.2.1pre22 to: http://violet.ibs.com.au/openssh/files/ This release consists of portability fixes and cleanups. It also resolves two issues which may have caused security problems - If you OS header files did not define PATH_STDPATH, then an unsafe path was used by default (it contained an implicit '.'). Thanks

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have just uploaded 1.2.1pre22 to: http://violet.ibs.com.au/openssh/files/ This release consists of portability fixes and cleanups. It also resolves two issues which may have caused security problems - If you OS header files did not define PATH_STDPATH, then an unsafe path was used by default (it contained an implicit '.'). Thanks

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

Solaris 7 doesn't have a ut_host element in utmp...patch let's bsd-login.c compile with this knowledge: *** openssh-1.2pre13.orig/bsd-login.c Fri Nov 19 00:32:34 1999 --- openssh-1.2pre13/bsd-login.c Fri Nov 19 14:23:49 1999 *************** *** 40,45 **** --- 40,46 ---- static char *rcsid = "$Id: bsd-login.c,v 1.1 1999/11/19 04:32:34 damien Exp $"; #endif /*

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

Unfortunately, the login.c changes after pre-19 have exposed some more NetBSD-centric problems concerning the lack of several fields in struct utmp. Here's another set of patches to fix NetBSD compiling (although they may also help some other UNIXes as well). Thanks, David --- configure.in.orig Mon Dec 27 09:09:05 1999 +++ configure.in Mon Dec 27 09:13:39 1999 @@ -264,6 +264,16 @@

This is about 90% of the core work. I omited a few files from the patch set since they are basicly small blocks of #ifndef HAVE_NEXT/#endif to get it to compile. Daimen, feel free to let me know what you applied and what your rejecting and why.. so I can work on cleaning things up. Andre, Only thing of note you may want to look into is NeXT does not use "ut_user" in it's lastlog.

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

Okay, everything as the first large one I sent today, with a few extra mods. _PATH_MAILDIR is only used in sshd.c, that I can see, so moved the #ifdef from config.h.in to there. several files had __progname defined in the middle of the code, as well as at the top of the code, so cleaned those out. all the fixes for u_int32_t -> uint32_t and u_int16_t -> uint16_t, plus added appropriate

Dear OpenSSH porting developers, finally I succeded in porting OpenSSH to QNX 4. To get things going I had to take over some definitions from Linux' include files, since they are not available under QNX (e.g. the howmany makro, NFDBITS, the lastlog structure). With this email I send a patch with all my changes as well as the file "qnx-term.h" which I created because IXANY and

Hi all, I've hacked in some better logging for what's going on with my logins and utmp/wtmp. Everything seems OK except for u.ut_host. In my case, the actual variable host for this test case is aragon.cheshirelaw.com. This is fine (as my logs show): Mar 5 21:22:47 frodo sshd[10274]: Actual: 983852567 /dev/ttyp0 aragon.cheshirelaw.com However, check out what u.ut_host is logged as:

On Thu, 30 Mar 2023, Fran?ois Ouellet wrote: > Hi, > > We need to limit concurrent sftp logins to one per user (because of bad > client behaviour). Is there any way to achieve this I have overlooked? > > It seems it could be possible with pam_limits, if sftp sessions were > recorded in utmp (a guess from what I found googling around). If I > configure

On Tue, 4 Apr 2023, Nico Kadel-Garcia wrote: > > We've been asked about this a number of times before - the problem is > > that utmp is really set up to record interactive logins that have a > > TTY/PTY assigned. There is AFAIK no real standard for recording > > "service logins" (e.g. sftp or SSH command execution w/o TTY) in utmp > > and many OS utmp