From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <cygwin@cygwin.com>
Subject: RE: [cygwin] openssh connection sharing fails: "mux_client_request_session: read from master failed: Connection reset by peer"
Date: Mon, 17 Jan 2022 11:59:59 -0500 [thread overview]
Message-ID: <032a01d80bc3$a9778420$fc668c60$@pdinc.us> (raw)
In-Reply-To: <032801d80bc2$8c6f3950$a54dabf0$@pdinc.us>
> -----Original Message-----
> From: Jason Pyeron
> Sent: Monday, January 17, 2022 11:52 AM
>
> > -----Original Message-----
> > From: Adam Dinwoodie
> > Sent: Monday, January 17, 2022 11:30 AM
> >
> > The SSH connection sharing function in Cygwin's openssh release, using
> > `ssh -M` or the ssh_config.5 ControlMaster configuration, doesn't appear
> > to work. Setting up a master connection seems fine, but subsequent SSH
>
> Sadly, it is a known issue.
>
> https://stackoverflow.com/questions/20959792/is-ssh-controlmaster-with-cygwin-on-windows-actually-possible/21439862#21439862
>
> We would be happy to thrown some $ or beer at it.
>
I should have posted the Cygwin.com link on this: https://cygwin.com/cygwin-ug-net/highlights.html#ov-hi-sockets
And for anyone looking to start - some food for thought:
https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
https://stackoverflow.com/questions/9475442/unix-domain-socket-vs-named-pipes
https://sourceware.org/legacy-ml/cygwin/2015-01/msg00123.html
-Jason
--
Jason Pyeron | Architect
PD Inc | Certified SBA 8(a)
10 w 24th St | Certified SBA HUBZone
Baltimore, MD | CAGE Code: 1WVR6
.mil: jason.j.pyeron.ctr@mail.mil
.com: jpyeron@pdinc.us
tel : 202-741-9397
next prev parent reply other threads:[~2022-01-17 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 16:29 Adam Dinwoodie
2022-01-17 16:52 ` [cygwin] " Jason Pyeron
2022-01-17 16:59 ` Jason Pyeron [this message]
2022-01-17 20:36 ` Adam Dinwoodie
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='032a01d80bc3$a9778420$fc668c60$@pdinc.us' \
--to=jpyeron@pdinc.us \
--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).