search for: client_setup_stdio_fwd

...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 co...

...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 co...

...et, wait for reply debug3: Received SSH2_MSG_IGNORE debug1: Server accepts key: pkalg ssh-rsa blen 533 debug2: input_userauth_pk_ok: fp 46:bb:2a:c2:29:72:ad:bc:a7:04:c8:8d:77:31:6f:5e debug3: sign_and_send_pubkey debug3: Received SSH2_MSG_IGNORE debug1: Authentication succeeded (publickey). debug3: client_setup_stdio_fwd cfe1:22 debug1: channel_connect_stdio_fwd cfe1:22 debug1: channel 0: new [stdio-forward] debug2: fd 4 setting O_NONBLOCK debug2: fd 5 setting O_NONBLOCK debug1: getpeername failed: Bad file descriptor debug1: Entering interactive session. debug3: Received SSH2_MSG_IGNORE channel 0: open failed: con...