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:	<02d501c29665$1b7d3950$78d96f83@pomello>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	<arBmind AT web DOT de>, <cygwin AT cygwin DOT com>
References:	<200211272159 DOT gARLxIX11334 AT mailgate5 DOT cinetic DOT de>
Subject:	Re: Bug in Cygwin SSHD on windows XP
Date:	Wed, 27 Nov 2002 22:34:11 -0000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

arBmind AT web DOT de <arBmind AT web DOT de> wrote:
> i want to report a serious bug in the current Cygwin SSH-Deamon
> implementation at Windows XP.

Works for me.

> error message (occurs on SSH-Client):
>> Last login: Wed Nov 27 21:43:22 2002 from localhost
>> G:\CygWin\bin\bash.exe: *** could not load wsock32, Win32 error 126

126 == DLL not found.

> how to reproduce this error:
> - you need windows XP (tested only on XP Professional, while win2k
> prof works well)
> - login with public key authorisation (error occurs imediately, no
> login possible)
> - login with password authorisation (works), and open another shell
> or sftp for this session (tested with the current "ssh.com"-client)

Works correctly for me.

> my investigations:
> - this error was reported 2 times here in the mailinglist:
>     http://sources.redhat.com/ml/cygwin/2002-11/msg00881.html
>     http://sources.redhat.com/ml/cygwin/2002-07/msg01745.html
>
>   but at no time followed by further investigations, due to
> report-issues
>    - no answer was posted
>    - the bug is still around
>    - and no entry on the known bugs list deals with this issue

Because vague bug reports are all we have. And no-one can reproduce it
either.

Try:
Making sure C:\WINDOWS\system32 is in the system PATH.
Making sure that 'Everyone' has at least 'Read & Execute' perms on
wsock32.dll

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -