X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.5 required=5.0	tests=AWL,BAYES_00,SPF_NEUTRAL
X-Spam-Check-By: sourceware.org
Message-ID: <4F294184.9030805@cs.utoronto.ca>
Date: Wed, 01 Feb 2012 08:43:32 -0500
From: Ryan Johnson <ryan DOT johnson AT cs DOT utoronto DOT ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: IBM ssh gateway
References: <201202011046 DOT 40681 DOT swampdog AT ntlworld DOT com>
In-Reply-To: <201202011046.40681.swampdog@ntlworld.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

On 01/02/2012 5:46 AM, Guy Harrison wrote:
> Hi Folks,
>
> Can anyone help interpret this? I am fairly certain the problem lies with
> IBM but I am no crypto expert. Is (for instance) the server rejecting the
> connection because (say) it does not understand ECDSA? Unfortunately I do
> not have an older instance of cygwin ssh to try that theory out. The
> failure is recent. I upgraded my cygwin instances over xmas.
>
> My primary concern is that the latter (linux) connection (after ~~~) may
> fail after a future upgrade.
I would definitely check with your local network security folks. When I 
was last at IBM I had trouble connecting from a certain machine -- just 
that one -- and nobody could figure out why. Finally, it turned out that 
I had a lot of locales installed and the long list of supported 
languages announced by my ssh client triggered some firewall rule.

Meanwhile, have you tried using `ssh -i' with a different key type? That 
should clarify whether it's an ECDSA issue, at least.

Ryan


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