X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:from:to:subject:date:in-reply-to
	:references:content-type:content-transfer-encoding:mime-version;
	 q=dns; s=default; b=Dg8xWK0v2UBPF5H0dXgjD8JD6xlAGTG0UWUBMC/+Fy9
	JcYRlKSWfatpzNVbz8AJQgNje/W1dlNymLuWqPLVcurFXq0tF9xn51eGIMEId/47
	+gDTJkjm5PGGT4H7q3mPGzzOSH7z019AcKY3KP40GUQav7DNRM+5+wH8OomPz+Vc
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:from:to:subject:date:in-reply-to
	:references:content-type:content-transfer-encoding:mime-version;
	 s=default; bh=SBkcfsnQ5pFhP+rL0j4FNGGGkS8=; b=fyX5QAIradOJJe7Gk
	bmagJrXiUj5LyFR8eEze0RgH/0PqSChSqHDJX/1Oj1D6EPPhzROJKfetUxYciT2K
	MpE5k+5IwyQnVTvegnCn5B2AeMMgfYwSzhtdgXbGT0osz+mLADQ0FLYY7fSrpFkY
	ZeMxHxeTAH6FteXR9ft/B8YHLg=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.7 required=5.0 tests=AWL,BAYES_40,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: blu0-omc4-s10.blu0.hotmail.com
X-TMN: [hIWNiMMDJXLAg+cAO6dbV2YYFMGjeWRq]
Message-ID: <BLU173-W9BF40E0ADBC0026E29769B59A0@phx.gbl>
From: Karl M <karlm30@hotmail.com>
To: "schulman.andrew@epa.gov" <schulman.andrew@epa.gov>,
        "cygwin@cygwin.com"	<cygwin@cygwin.com>
Subject: RE: OpenSSH port forwarding bug
Date: Wed, 19 Feb 2014 17:18:44 -0800
In-Reply-To: <BLU173-W51D2527ADA38BFF2E88A7FB59F0@phx.gbl>
References: <BLU173-W3896EF675E0B97DFB4B04DB59D0@phx.gbl>,<8tfof9t4krrjbrj9rk14umcjbh05h2msko@4ax.com>,<BLU173-W34071B5D95ADF6D2547C49B59C0@phx.gbl>,<BLU173-W51D2527ADA38BFF2E88A7FB59F0@phx.gbl>
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id s1K1J5b9009139

> Subject: RE: OpenSSH port forwarding bug
> Date: Fri, 14 Feb 2014 22:11:03 -0800
>
>> Subject: RE: OpenSSH port forwarding bug
>> Date: Fri, 14 Feb 2014 12:48:53 -0800
>>
>> Hi Andrew...
>>
>> This is what I usually use in a proxycommand. So the example localized
>> it to just one layer. You can see that it connects to an ssh server and
>> then drops when I fail to complete the handshake. That is expected.
>>
>> The example shows that ssd -W gives an error, but doing the same thing
>> with ssh nc works fine.
>>
>> Thanks,
>>
>> ...Karl
>>
>>> Subject: Re: OpenSSH port forwarding bug
>>> Date: Wed, 12 Feb 2014 22:44:54 -0500
>>>
>>>> Hi All...
>>>> The following example shows the port forwarding problem.
>>>>
>>>>
>>>> ~
>>>>
>>>> $ ssh raven -W coyote:22
>>>> getsockname failed: Bad file descriptor
>>>> SSH-2.0-OpenSSH_6.5
>>>> Protocol mismatch.
>>>> ~
>>>>
>>>> $ ssh raven nc coyote 22
>>>> SSH-2.0-OpenSSH_6.5
>>>> Protocol mismatch.
>>>
>>> What are you trying to do?
>>>
>>>
>>> --
> --
Hi All...

So I solved my real problem. It was a typo in my .ssh/config file that prevented me from being able to use the proxy command in ssh. I've used it for years.

But there is still a minor bug in ssh, When I use a proxycommand with ssh with the -W option, to avoid using an external program such as netcat (nc) the error message "getsockname failed: Bad file descriptor" is displayed. The proxycommand works, but displays this error message. Using netcat does not display this error message.

The example above is a STC showing the error in a more easily visible way. The names raven and coyote are local names on my network at home.

I am wishing the error message into the cornfield.

Thanks,

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


