ricky at rzhou
Oct 13, 2011, 2:18 AM
Post #1 of 2
As reported earlier at
[PATCH] Fix control persist and stdio forward interaction
there is some strange interaction between ControlPersist and ssh -W that
breaks things if you're using both. Specifically, ssh -W host:port with
ControlPersist enabled opens up two connections to host:port and sends
data from both back.
I think this is happening because channel_connect_stdio_fwd is being
called twice, once in client_setup_stdio_fwd, which is called from
ssh_init_forwarding, and once in process_mux_stdio_fwd, which is
called once the client process starts talking to the master process.
It looks like the way ControlPersist is implemented, the process forks,
with the child becoming the master process and the child making its
connection through that. Thus, it seems like a reasonable fix to not
call client_setup_stdio_fwd if need_controlpersist_detach is set, and
just allow it to happen later.
Does the attached patch look OK?