similar to: [Bug 337] utmp/wtmp logging

http://bugzilla.mindrot.org/show_bug.cgi?id=337 Summary: utmp/wtmp logging Product: Portable OpenSSH Version: 3.1p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: thomas at

Hi, For each user connection when privilege separation is enabled, 3 processes are of interest for this topic. 1. sshd:[priv] - privileged user process. 2. sshd:user at pts/0 - user process. 3. shell - shell process. Openssh code writes the #2. sshd:user at pts/0 - user process to the utmp/wtmp file. Is this the correct behaviour.? Or should it write the #3. shell

Good day - I've checked where I can think to check, but I can find no mention of wtmp/utmp being supported in the standard Samba release at all. The closest I got was a posting from Joshua Lewis <jlewis@iosphere.net> dated Fri, 19 Jul 1996 08:06:55 -0400 (EDT) (almost exactly a year ago) which states in the final paragraph: > On another note, look for UTMP/WTMP support in Samba

Hi! I am resending the following message about problems with utmp handling. * In the meantime I had some request in private mail from people asking whether I have new information. * The problem is still persistant in 2.9p2. * My own new investigations show, that the problem only appears with protocol 2, not with protocol 1, I therefore only started to note it when protocol 2 became the

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

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

Hi! I have updated to OpenSSH 2.9p1 on HP-UX 10.20. Since this update, I seem to have problems with utmp/wtmp handling, in that entries are not removed as expected. ws01 36: w 10:06am up 76 days, 12:52, 12 users, load average: 0.17, 0.25, 0.20 User tty login@ idle JCPU PCPU what ... root pts/8 5:28pm159:41 - ... ws01 37: ps -ef | grep pts/8

I have just tarred up a snapshot and uploaded it to: http://www.mindrot.org/misc/openssh/openssh-SNAP-20000823.tar.gz The snapshot incorporates the last month's fixes and enhancements from the openssh-unix-dev mailing list and from the OpenBSD developers. In particular: - ssh-agent and ssh-add now handle DSA keys. NB. this does not interop with ssh.com's ssh-agent. (Markus Friedl)

Hi, I've got a 2.8-RELEASE box that uses the old utmp.h with: #define UT_NAMESIZE 8 #define UT_LINESIZE 8 #define UT_HOSTSIZE 16 2.5.1's ssh/login.c seems use this by including <utmp.h>. However, when a remote user logs into this box, the wtmp file is munged from that point on. There are no notes about this on the OpenSSH site ("OpenSSH compiles cleanly

I've noticed rather strange wtmp logging behavior in sshd. Can anyone confirm or solve the following: Once a user authenticates themself to sshd, sshd among other things records the login in the wtmp, which `last` reads. However, sshd logs hostnames which are longer than 16 characters instead of IPs like normal programs would. As a result, I have useless entries such as: tempest

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:

I spent some time with 3.0.2p1 to discover why OpenSSH on HP/UX 11.00 64-bit corrupts the /var/adm/wtmp file. The problem is with the utmp structure itself. When building with 32-bit compilation flags, the size of the utmp structure is 60 bytes. When building under 64-bit, the size is 72 bytes. The size difference is due to structure alignment and using basic types whose size changes depending

removes HAVE_BOGUS_SYS_QUEUE_H and always use our queue.h. ok? Index: acconfig.h =================================================================== RCS file: /var/cvs/openssh/acconfig.h,v retrieving revision 1.122 diff -u -r1.122 acconfig.h --- acconfig.h 26 Feb 2002 16:40:49 -0000 1.122 +++ acconfig.h 12 Mar 2002 02:11:39 -0000 @@ -14,7 +14,6 @@ /* SCO workaround */ #undef

Hello all, I use a Slackware 4.0 based system (libc5 based, with glibc2.07 runtime support). I've configured OpenSSH using: ./configure --sysconfdir=/etc/ssh --without-pam --with-default-path=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbi n:/sbin NOTE: yes, --with-default-path DOES work, since pre24 (pre 22 did not) When I try to compile OpenSSH-1.2.1pre25 (or pre24 or pre22), I

http://bugzilla.mindrot.org/show_bug.cgi?id=120 ------- Additional Comments From markus at openbsd.org 2002-02-19 04:29 ------- can you allocate ptys as non-root? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

Hi all! wtmp entries are generated when loggin into a system without a command, e.g. "ssh -l user system". When using an additional command executed by ssh on the "other side", no wtmp entry will be generated. So the command "ssh -l user system /bin/csh" will not generate a wtmp entry but the user is logged in ... I have the problem right know. The users are starting

Portable OpenSSH 4.3p2 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol version 1.3, 1.5 and 2.0 implementation and includes sftp client and server support. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or

Hi, On Linux, glibc is using a 32bit time_t for wtmp and similar structs even on a 64bit system: https://www.thkukuk.de/blog/Y2038_glibc_utmp_64bit/ https://www.thkukuk.de/blog/Y2038_glibc_wtmp_64bit/ Since the glibc developers stated that they don't plan to solve the problem in glibc, but think that this interfaces are legacy and should be removed from glibc (like musl libc, which does not

hello tried the archives without success so hoping someone remember the fix. if compiled 64 bits openssh will not add a correct entry in wtmpx and the data/info get corrupted... so someone remembers what needed to be done to fix this? thanks -ls

http://bugzilla.mindrot.org/show_bug.cgi?id=980 ------- Additional Comments From senthilkumar_sen at hotpop.com 2005-04-29 00:28 ------- I tried passing SIGTERM to the sshd user process after applying the patch (id=821) and it is not cleaning up the wtmp entries. What would be needed in the patch additionaly so that proper pid is passed at the time of cleaning wtmp entries when SIGTERM is