On Feb 19 17:18, Karl M wrote: > >>> 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.
Cygwin's getsockname is called with a file descriptor -1. I tried it on Linux and it occurs with the 6.5p1 version as well so it's a generic problem, still present upstream. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
pgpP722tXJ2li.pgp
Description: PGP signature
