X-Spam-Check-By:	sourceware.org
Date:	Mon, 12 Mar 2007 09:20:15 +0100 (MET)
From:	Angelo Graziosi <Angelo DOT Graziosi AT roma1 DOT infn DOT it>
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] Updated: OpenSSH-4.6p1-1: Problems!
Message-ID:	<Pine.OSF.4.21.0703120912010.17095-100000@ax0rm1.roma1.infn.it>
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Corinna Vinschen wrote:

> I suggest to take the opportunity to switch to protocol 2 which is
> the better and safer protocol anyway.


I wrote:

> I have tried, but :
>
> $ ssh -2 graziosi AT hostname
> Protocol major versions differ: 2 vs. 1
>
> (openssh-4.5p1-1 with -2 gives the some result)
>
> While
>
> $ ssh graziosi AT hostname
> Disconnecting: Corrupted check bytes on input.


I contacted the administrator of 'hostname' and he confirmed that
'hostname' accepts only the option '-1' with ssh (even if it would be
better to use -2)!

Using '-2' toward another machine, it works!

So the conclusion is that openssh-4.6p1 seems to have a bug only with
option '-1'.


Cheers,

   Angelo.


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