From: Adam Dinwoodie <adam@dinwoodie.org>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Feature request: File descriptor support by sockets.
Date: Sat, 8 Oct 2022 14:19:41 +0100 [thread overview]
Message-ID: <CA+kUOamq5aidTFqeA2N=y72486_JZZdfmPaUytQcKR25UK80FA@mail.gmail.com> (raw)
In-Reply-To: <BY5PR10MB418011A882FE4A6C4433BCD2FF5C9@BY5PR10MB4180.namprd10.prod.outlook.com>
On Thu, 6 Oct 2022 at 18:37, Darren Whobrey wrote:
>
> Hi, I'm using the latest version of Cygwin (3.3.6) and the Cygwin OpenSSH (OpenSSH_9.0p1, OpenSSL 1.1.1q 5 Jul 2022) version of ssh to talk to hosts using ControlMaster connection sharing. This uses sockets behind the scenes. When ControlMaster is set to no, the connection is successful.
>
> Ssh connections are failing at the point where IO starts to be forwarded to the host.
>
> Here's a snippet of log output from "ssh -vvv some-host":
>
> <snip>
>
> When successful connections are made from an OL7 client (with older version of OpenSSH, but mux commands are similar), comparative logs are:
>
> <snip>
>
> According to this web posting, it suggests the bug lies with "file descriptors over unix sockets do not work in Cygwin":
> https://exchangetuts.com/is-ssh-controlmaster-with-cygwin-on-windows-actually-possible-1639696447917488
>
> Is this something that can be fixed?
I'm very confident it *can* be fixed! But this gap has existed since
at least 2009 (see
https://cygwin.com/pipermail/cygwin/2012-February/199995.html and
https://sourceware.org/legacy-ml/cygwin/2009-10/msg00397.html) so I
suspect that, unless you're proposing to do the work or pay someone to
do it on your behalf, it's unlikely to happen any time soon.
prev parent reply other threads:[~2022-10-08 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 17:36 Darren Whobrey
2022-10-08 13:19 ` Adam Dinwoodie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+kUOamq5aidTFqeA2N=y72486_JZZdfmPaUytQcKR25UK80FA@mail.gmail.com' \
--to=adam@dinwoodie.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).