Bug#731950: ssh -g has no effect if master socket already open

2013-12-11 Thread Russ Allbery
Ken Sharp writes: >> So far as I can tell, this is true for all port forwarding when used >> with ControlMaster. Across the board, it appears that all port >> forwarding has to be specified on the original connection and is >> ignored for subsequent connections. > No I can add as many port forw

Bug#731950: ssh -g has no effect if master socket already open

2013-12-11 Thread Ken Sharp
So far as I can tell, this is true for all port forwarding when used with ControlMaster. Across the board, it appears that all port forwarding has to be specified on the original connection and is ignored for subsequent connections. No I can add as many port forwards as I like after the master

Bug#731950: ssh -g has no effect if master socket already open

2013-12-11 Thread Russ Allbery
Ken Sharp writes: > However, if it isn't then -g is ignored on subsequent attempts to forward > ports: So far as I can tell, this is true for all port forwarding when used with ControlMaster. Across the board, it appears that all port forwarding has to be specified on the original connection an

Bug#731950: ssh -g has no effect if master socket already open

2013-12-11 Thread Ken Sharp
Package: openssh-client Version: 1:5.9p1-5 Control: found -1 1:6.4p1-1 From the man page: -g Allows remote hosts to connect to local forwarded ports. When working with a control socket, this works fine if -g is included with the initial connect attempt, for example: $ cat ~/.ssh/config