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: <3DDB655E.6070004@isg.de>
Date: Wed, 20 Nov 2002 11:35:10 +0100
From: Tino Lange <tino DOT lange AT isg DOT de>
Organization: IS Innovative Software AG
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021113
X-Accept-Language: de, en-us, en, fr
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"
References: <20021116174458 DOT A10374 AT ping DOT be> <3DD67E8F DOT 25627B1D AT isg DOT de>
In-Reply-To: <3DD67E8F.25627B1D@isg.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

Hi Cygwin-List!

Just discoverd that the same problem exists with ".ssh/authorized_keys2".

Can someone reproduce the problem?

Cheers,

Tino

---------------------

Tino Lange wrote:
> Hi again!
> 
> I have some new problems with sshd on Windows 2000.
> (all latest cygwin packages from today)
> 
> I try to login on my Win 2000 machine from my Linux machine. Works fine
> so far. (Thanks for your recent help!)
> But: if I use RSA authentication with "authorized_keys" to get on the
> cygwin machine it still works but I don't have network/sockets - the
> windows socket interface cannot be initialized?!
> 
> If I remove "authorized_keys" and login via password it works again.
> Strange, or?
> 
> Here's a copy and paste:
> 
> tino AT tinux:~ > ssh tinont
> Tino AT tinont's password:
> Last login: Sat Nov 16 18:12:09 2002 from tinux.tino-lange.de
> Fanfare!!!
> You are successfully logged in to this server!!!
> 
> Tino AT TINONT ~
> $ ping tinux
> 
> Ping tinux [192.168.1.1] mit 32 Bytes Daten:
> 
> Antwort von 192.168.1.1: Bytes=32 Zeit<10ms TTL=64
> Antwort von 192.168.1.1: Bytes=32 Zeit<10ms TTL=64
> 
> Ping-Statistik f�r 192.168.1.1:
>     Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
> Ca. Zeitangaben in Millisek.:
>     Minimum = 0ms, Maximum =  0ms, Mittelwert =  0ms
> 
> Tino AT TINONT ~
> $ cat .ssh/identity.pub > .ssh/authorized_keys
> 
> Tino AT TINONT ~
> $ chmod 644 .ssh/authorized_keys
> 
> Tino AT TINONT ~
> $ logout
> Connection to tinont closed.
> 
> tino AT tinux:~ > ssh tinont
> Last login: Sat Nov 16 18:12:51 2002 from tinux.tino-lange.de
> Fanfare!!!
> You are successfully logged in to this server!!!
> 
> Tino AT TINONT ~
> $ ping tinux
> Fehler bei der Initialisierung der Windows-Socketsschnittstelle.
> Fehlercode 0.
> 
> Tino AT TINONT ~
> $ rm .ssh/authorized_keys
> 
> Tino AT TINONT ~
> $ logout
> Connection to tinont closed.
> 
> tino AT tinux:~ > ssh tinont
> Last login: Sat Nov 16 18:12:51 2002 from tinux.tino-lange.de
> Fanfare!!!
> You are successfully logged in to this server!!!
> 
> Tino AT TINONT ~
> $ ping tinux
> 
> Ping tinux [192.168.1.1] mit 32 Bytes Daten:
> 
> Antwort von 192.168.1.1: Bytes=32 Zeit<10ms TTL=64
> Antwort von 192.168.1.1: Bytes=32 Zeit<10ms TTL=64
> 
> Ping-Statistik f�r 192.168.1.1:
>     Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
> Ca. Zeitangaben in Millisek.:
>     Minimum = 0ms, Maximum =  0ms, Mittelwert =  0ms
> 
> Tino AT TINONT ~
> $
> 
> Do you have an idea?
> Thanks!
> 
> Tino


--
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/