sshd hanging after multiple successive logons

douglas.manton at uk.ibm.com douglas.manton at uk.ibm.com
Wed Jan 24 04:51:01 EST 2001




Damien,

I am still running the test, so haven't had a chance to test the snapshot
yet.  Will do after I have investigated the following:

I have found a clue in my syslog:

Jan 22 18:33:00 myserver sshd[30586]: Accepted rsa for myuser from
10.0.0.1 port 57453
Jan 22 18:33:03 myserver sshd[30632]: Accepted rsa for myuser from
10.0.0.1 port 57454
Jan 22 18:33:05 myserver sshd[30678]: Accepted rsa for myuser from
10.0.0.1 port 57455
Jan 22 18:33:07 myserver sshd[30468]: Accepted rsa for myuser from
10.0.0.1 port 57456
Jan 22 18:33:09 myserver sshd[30514]: Accepted rsa for myuser from
10.0.0.1 port 57457
Jan 22 18:33:11 myserver sshd[20990]: Generating new 768 bit RSA key.
Jan 22 18:33:11 myserver sshd[30560]: Accepted rsa for myuser from
10.0.0.1 port 57458
Jan 23 08:56:16 myserver sshd[25084]: Server listening on 0.0.0.0 port 22.
Jan 23 08:56:16 myserver sshd[25084]: Generating 768 bit RSA key.
Jan 23 08:56:18 myserver sshd[25084]: RSA key generation complete.

Note how the daemon hangs when the user connects to the second a new RSA
key is generated.  The key generation never completes.  The morning entry
was my killing and restarting of the daemon.

Coincidence?

Many thanks,
--------------------------------------------------------
 Doug Manton, AT&T EMEA Firewall and Security Solutions

                   E:  demanton at att.com
--------------------------------------------------------
"If privacy is outlawed, only outlaws will have privacy"

On Tue, 23 Jan 2001, Damien Miller wrote:

> On Tue, 23 Jan 2001 douglas.manton at uk.ibm.com wrote:
>
> > The problem is that after so many connections, the parent sshd hangs
and
> > does not accept any more connections.  I have reproduced the problem
using
> > a simple shell script on my local machine:
>
> I am running something similar now (770 connections and counting).
>
> What version of OpenSSH are you running? If you can, please try the
> snapshot[1] and see if that resolves the problem.







More information about the openssh-unix-dev mailing list