similar to: logging in

On Tue, Jan 30, 2018 at 12:26 PM, <m.roth at 5-cent.us> wrote: > This is.... odd. > > We're seeing a *lot* of > sshd[8400]: Timeout, client not responding. > So I'm trying to find out whose client is having issues. Trying to figure > that, after processes are gone, I tried looking in lastlog, which is where > it gets odd. lastlog shows root coming in, and it

The new login code works fine with AIX 4.3. Two nits, though. If --disable-lastlog is defined, the code still tries to slog through wtmp to determine the last login time. Is this a bug or a feature? If a feature, change the DISABLE_LASTLOG test below to WITH_AIXAUTHENTICATE. Also, a small typo in configure.in, plus an AIX tweak. --- configure.in.orig Thu Jun 8 21:58:35 2000 +++ configure.in Mon

https://bugzilla.mindrot.org/show_bug.cgi?id=1774 Summary: wtmp and lastlog on AIX Product: Portable OpenSSH Version: 5.5p1 Platform: All OS/Version: AIX Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: unassigned-bugs at mindrot.org ReportedBy: defrayable at

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

Hi, I found a bug in all versions of SSH. I'll give you an example when the bug occurs. When I connect to a remote computer using 'ssh user at host.somewhere.in.th.net.com /bin/bash' (or /bin/tcsh) I log into the remote computer and SSHD doesn't log this in wtmp,utmp,secure and lastlog. It's *only* visible in /var/log/messages. That's all I want to tell You. I hope

Hi all, please, is there some utility/command/... to list all installed kernel modules ? Peter Rosa

Hello, already checked the Mailinglist archive for HPUX Problems, but havent found exact this: ./configure --prefix=/opt --without-pam --with-ssl-dir=/opt/OpenSSL --with-lastlog=/var/adm/wtmp --with-egd-pool=/dev/entropy --with-tcp-wrappers --with-pid-dir=/var/run --sysconfdir=/etc/ssh and get after a make: gcc -O2 -Wall -D_HPUX_SOURCE -I/usr/local/include -I/opt/include

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

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

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

that only works when you are presuming that the host was not hacked already because i would clear those logs when i hacked a system :) but indeed it's a try, If you remain unsure, it is best to reinstall the system to be sure that a fresh and newly updated (yeah update it when installed :)) system is not compromised at that time.. loads of work, but it gives you some relief to know that

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

Please carbon-copy me on replies. For some reason, my wtmp is never updated when I login via openssh. Some information about my system: Linux kernel 2.6.9 running glibc-2.3.4. And the opensshd is openssh-3.9p1 (pkgsrc package openssh-3.9.1nb6). $ ls -l /var/log/lastlog /var/log/wtmp /var/run/utmp -rw-rw-r-- 1 root utmp 29492 May 25 13:12 /var/log/lastlog -rw-rw-r-- 1 root

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

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

Greetings, I am seeing strange entries when i perform "last -20" for example. Here's a sample output becuase I can not seem to make any sense out of this in the last two days and can't find any information online. Any help is appreciated. 0 F=?Bttyp Wed Dec 31 16:00 still logged in 0 6??Bttyp Wed Dec 31 16:00

There are a couple of bugs in the openssh-3.7.1p2. The aix_setauthdb function does not work with other types of authentication such as AFS/DFS. The loginfailed test in configure is not correct. Also, AIX can use the wtmp logging which I added in configure. Attached is the patch. Thanks, Matt Richards -------------- next part -------------- *** openssh-3.7.1p2/openbsd-compat/port-aix.c Mon Jul 14

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, Can any of you explain this weirdness: [root at machine log]# cd /var/log/ [root at machine log]# ls -la|grep last -r-------- 1 root root 1254130450140 Nov 6 21:44 lastlog [root at machine log]# du -hs lastlog 52K lastlog What's up with the output of ls? This is x86_64. Thanks, Morten