Date: Mon, 14 Sep 1998 09:02:30 -0700 (PDT) From: Roger Marquis <marquis@roble.com> To: freebsd-security@FreeBSD.ORG Subject: Re: sshd Message-ID: <Pine.SUN.3.96.980914085125.27468B-100000@roble.com> In-Reply-To: <Pine.BSF.4.00.9809140219060.4728-100000@super-g.inch.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 14 Sep 1998, spork wrote: > Number of times sshd died: 0 > ... A common data point but there's also the shell that is spawned by sshd and applications spawned by the shell. Any of those can hang a session too. The most common problem I've seen is corrupt terminal definitions that no combination of setenv, tset and reset will fix. > If you really need a backup access method, get a console server :) Have that too but there are many situations where it's not feasible. The real issue, it seems to me, is consistency. If ftp, telnet, rsh, rlogin, etc. run from inetd then sshd should also. The original reason it wasn't is the key generation delay, which isn't an issue on anything faster than a 486/25. Roger Marquis Roble Systems Consulting http://www.roble.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.96.980914085125.27468B-100000>