On Sun, 18 Nov 2018 at 19:26, Matthieu Herrb wrote:
> This fixes the issue for me yes.
> Thanks.
>
Thanks all, diff has been committed.
--
Darren Tucker (dtucker at dtucker.net)
GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 37F4 9357 ECEF 11EA A6FA (new)
Good judgement comes with experience
On Sun, Nov 18, 2018 at 10:10:30AM +1100, Darren Tucker wrote:
> On Sun, Nov 18, 2018 at 10:03:20AM +1100, Darren Tucker wrote:
> > On Sun, 18 Nov 2018 at 09:48, Darren Tucker wrote:
> >
> > > Was able to reproduce and confirmed by bisecting that the "redirect stderr
> > > of ProxyCommands to /de
On Sun, Nov 18, 2018, 11:04 Damien Miller ok djm
>
> why does mosh depend on the stderr of a proxycommand?
>
Based on my extensive (ie 5 minute) study of the code, it's turtles all the
way down. mosh invokes ssh with a proxycommand that invokes mosh again in
a different mode, my guess is so that
ok djm
why does mosh depend on the stderr of a proxycommand?
On Sun, 18 Nov 2018, Darren Tucker wrote:
> On Sun, Nov 18, 2018 at 10:03:20AM +1100, Darren Tucker wrote:
> > On Sun, 18 Nov 2018 at 09:48, Darren Tucker wrote:
> >
> > > Was able to reproduce and confirmed by bisecting that the "re
On Sun, 18 Nov 2018 10:10:30 +1100, Darren Tucker
wrote:
> On Sun, Nov 18, 2018 at 10:03:20AM +1100, Darren Tucker wrote:
> You can work around it by setting ControlPersist=yes either in
> ~/.ssh/config or via mosh's --ssh option.
> ok?
This diff makes mosh work again, thanks!
(ok danj@ fwi
On Sun, Nov 18, 2018 at 10:03:20AM +1100, Darren Tucker wrote:
> On Sun, 18 Nov 2018 at 09:48, Darren Tucker wrote:
>
> > Was able to reproduce and confirmed by bisecting that the "redirect stderr
> > of ProxyCommands to /dev/null when ssh is started with ControlPersist"
> > change is where it br
On Sun, 18 Nov 2018 at 09:48, Darren Tucker wrote:
> Was able to reproduce and confirmed by bisecting that the "redirect stderr
> of ProxyCommands to /dev/null when ssh is started with ControlPersist"
> change is where it breaks, but I don't understand what mosh is doing under
> the covers that n
Was able to reproduce and confirmed by bisecting that the "redirect stderr
of ProxyCommands to /dev/null when ssh is started with ControlPersist"
change is where it breaks, but I don't understand what mosh is doing under
the covers that now doesn't work. Will look further.
--
Darren Tucker (dtuc
On Sat, Nov 17, 2018 at 09:47:19PM +1100, Darren Tucker wrote:
> On Sat, 17 Nov 2018 at 18:29, Matthieu Herrb wrote:
>
> > on amd64-current on the client side, mosh now fails to connect to
> > remote hosts :
> >
> > /usr/local/bin/mosh: Did not find remote IP address (is SSH ProxyCommand
> > disa
On Sat, 17 Nov 2018 at 18:29, Matthieu Herrb wrote:
> on amd64-current on the client side, mosh now fails to connect to
> remote hosts :
>
> /usr/local/bin/mosh: Did not find remote IP address (is SSH ProxyCommand
> disabled?).
> Exit 10
>
What does the client's ~/.ssh/config look like for that
Hi,
on amd64-current on the client side, mosh now fails to connect to
remote hosts :
/usr/local/bin/mosh: Did not find remote IP address (is SSH ProxyCommand
disabled?).
Exit 10
The remote host has not changed its configuration (It's an OpenBSD 6.2
machine that I haven't upgraded or rebooted y
11 matches
Mail list logo
