search for: ut_names

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

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 14:24:20 2004 +++ /home/mickey/utmp.c Wed Mar 30 15:51:40 2005 @@ -261,6 +261,7 @@ } #ifndef HAVE_PUTUTLINE +#include <ttyent.h>

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

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

At 08:15 04/07/00 +0200, Bladt Norbert wrote: >> Darren Evans [SMTP:darren at horseplay.demon.co.uk] wrote: >> >> gcc -g -O2 -Wall -I/usr/local/ssl/include -DETCDIR=\"/usr/local/etc\" >-DSSH_PROGRAM=\"/usr/local/bin/ssh\" - >> DSSH_ASKPASS_DEFAULT=\"/usr/local/libexec/ssh/ssh-askpass\" >-DHAVE_CONFIG_H -c loginrec.c >> loginrec.c:

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

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

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

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

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.

...1349 ---- #define LL_FILE 1 #define LL_DIR 2 #define LL_OTHER 3 + + /* struct lastlog is not defined under QNX: define it */ + #if defined(__QNX__) && !defined(__QNXNTO__) + #define __time_t time_t + + /* from Linux's <bits/utmp.h> */ + #define UT_LINESIZE 32 + #define UT_NAMESIZE 32 + #define UT_HOSTSIZE 256 + + /* The structure describing an entry in the database of + previous logins. */ + struct lastlog + { + __time_t ll_time; + char ll_line[UT_LINESIZE]; + char ll_host[UT_HOSTSIZE]; + }; + #endif /* __QNX__ && !__QNXNTO__ */ s...

...utmp)), SEEK_SET); /* * Prevent luser from zero'ing out ut_host. *************** *** 70,75 **** --- 74,80 ---- strncmp(old_ut.ut_line, utp->ut_line, UT_LINESIZE) == 0 && strncmp(old_ut.ut_name, utp->ut_name, UT_NAMESIZE) == 0) (void)memcpy(utp->ut_host, old_ut.ut_host, UT_HOSTSIZE); + #endif (void)lseek(fd, (off_t)(tty * sizeof(struct utmp)), SEEK_SET); (void)write(fd, utp, sizeof(struct utmp)); (void)close(fd); Marc G. Fournier...

Hi, i just want to know if it's possible (i guess it is) to see in a log file the logging (date and hour) of a user. I looked in /var/log/smbd.log, nmbd.log, machine.log but there is no record when the user pat (for example) loged in the network. Does someone knows ? Thanks.

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

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