Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: ssh client hanging after authn for interactive sessions

Subject: Re: ssh client hanging after authn for interactive sessions
Date: Tue, 23 Jan 2007 08:27:36 +1100
On Sun, Jan 21, 2007 at 08:22:05PM -0800, David Anderson wrote:
We're having some trouble on a linux ssh shell server. There are
currently 300 or so account, and when any sizable number of these
connect simultaneously, subsequent connections hang after
authentication for any interactive session.

Running non-interactive commands (say, `ls`) works fine, but running
anything interactive (tried bash and zsh in this case) hangs the
connection. When the connection is hanged, if the client is in verbose
mode, I see keepalive packets being transmitted regularly, so the
connection is there... Just not doing anything.

This has been reported for many different clients, including putty on
win32 and versions of openssh from 4.2 to 4.5 on linux, bsd and osx.
The server itself has "OpenSSH_4.2p1, OpenSSL 0.9.7l 28 Sep 2006"
installed.

Has anyone encountered this before? We suspect we're running into some
kind of resource limit, but ssh not explicitely failing or logging
anything unusual is making this hard to debug. Follows a transcript of
an openssh 4.2 trying to connect and get a shell:

I suspect that your server is running out of ptys.  Checking the server's
syslog should show errors if that's the case.

Depending on what vintage your Linux distro is you may need to mount
/dev/pts, add more pty device nodes in /dev or recompile the kernel with
more ptys.

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

<Prev in Thread] Current Thread [Next in Thread>