public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: OpenSSH-7.4p1-1
Date: Wed, 21 Dec 2016 08:56:00 -0000	[thread overview]
Message-ID: <20161221085623.GD28343@calimero.vinschen.de> (raw)
In-Reply-To: <CAFo71_6_9qrgn8L5Zg=m+_3pUz53SB321XPnAUuqJ=Ss+12-yg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2302 bytes --]

On Dec 20 23:46, Ismail Donmez wrote:
> On Tue, Dec 20, 2016 at 9:44 PM, Corinna Vinschen wrote:
> > I've just updated the Cygwin version of OpenSSH to 7.4p1-1.
> >
> > This is primarily an upstream bugfix release.
> >
> > Below's the original release message.
> [...]
> >  * ssh(1): Add a proxy multiplexing mode to ssh(1) inspired by the
> >    version in PuTTY by Simon Tatham. [...]
> 
> Looks like this could be used for connection multiplexing on Cygwin.
> Since it doesn't seem to be documented I am not sure how one can test
> it, but ...
> 
> with
> 
> 
> Host *
> ControlMaster auto
> ControlPath ~/.ssh/master-%r@%h:%p
> 
> latte ~ > ssh i10z.com
> mux_client_request_session: read from master failed: Connection reset by peer
> Failed to connect to new control master
> 
> --> Fails as expected, lets retry.
> 
> latte ~ > ssh i10z.com
> mux_client_request_session: read from master failed: Connection reset by peer
> ControlSocket /home/ismail/.ssh/master-ismail@i10z.com:22 already
> exists, disabling multiplexing
> Welcome to Ubuntu 16.10 (GNU/Linux 4.8.0-30-generic x86_64)
> 
>  * Documentation:  https://help.ubuntu.com
>  * Management:     https://landscape.canonical.com
>  * Support:        https://ubuntu.com/advantage
> Last login: Tue Dec 20 23:42:56 2016 from 2a02:810d:8ac0:a3c:de8:1380:f2c2:bc79
> 
> --> Started a new session and created the master too.
> 
> latte ~ > ssh -O proxy i10z.com
> Welcome to Ubuntu 16.10 (GNU/Linux 4.8.0-30-generic x86_64)
> 
>  * Documentation:  https://help.ubuntu.com
>  * Management:     https://landscape.canonical.com
>  * Support:        https://ubuntu.com/advantage
> Last login: Tue Dec 20 23:43:02 2016 from 2a02:810d:8ac0:a3c:de8:1380:f2c2:bc79
> 
> --> Started a new session.
> 
> latte ~ > ssh -O proxy i10z.com
> Last login: Tue Dec 20 23:43:06 2016 from 2a02:810d:8ac0:a3c:de8:1380:f2c2:bc79
> 
> --> Voila, it used the existing connection!
> 
> And after that it indeed seems to be using the old connection as long
> as you specify -O proxy option.
> 
> Something to play with I guess.

Neat.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-12-21  8:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-20 20:46 Corinna Vinschen
2016-12-20 22:46 ` Ismail Donmez
2016-12-21  8:56   ` Corinna Vinschen [this message]
2016-12-21 13:22 ` Frank Fesevur
2016-12-21 16:41   ` Corinna Vinschen
2016-12-21 17:39     ` Erik Soderquist
2016-12-21 18:25       ` Corinna Vinschen
2016-12-21 18:26       ` Brian Inglis

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=20161221085623.GD28343@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).