Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<000701c30467$504e30b0$632db150@uk.deloitte.com>
From:	"WireFreeBloke" <wirefreebloke AT yahoo DOT co DOT uk>
To:	<cygwin AT cygwin DOT com>
Subject:	OpenSSH 4 Win - spurious listener ports after conx established
Date:	Wed, 16 Apr 2003 23:27:02 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

I downloaded and installed the OpenSSH for Windows package
(http://lexa.mckenna.edu/) yesterday and it works fine, but I noticed some
strange behaviour from the sshd when a connection is established.

I installed the server on XP pro, and have connected to it using Putty and
plink from a 2k box.

When an ssh connection is established, running netstat -an on the XP box
shows that ports >1024 are
being opened as listner services and then closed after a fraction of a
second, and then the next available port is opened and so on. Looking at the
firewall stats I can see that it is the ssh daemon that owns these ports.

I stopped the sshd service and launched sshd.exe from a cmd.exe instead and
found that it did not bind to these user ports, but it would seem unlikely
that cygrunsrv is at fault.

Has anyone seen this before, or got any idea why the sshd would be
continually opening these listening ports?

Many thanks
Martin



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -