ControlPath in ssh_config fails v0.0.3.0

[dougransom]

ssh config

Host blue
HostName underdoug.ca
User underdou
ControlPath c:/users/doug/.ssh/controlmasters_doug_blue
ControlMaster auto
ControlPersist 10m

c:\Program Files\OpenSSH>ssh blue
muxclient socket(): Unknown error

[manojampalam]

ControlMaster is not supported on Windows yet. See https://github.com/PowerShell/Win32-OpenSSH/wiki/Project-Scope

[opoplawski]

Would be nice.

[dobsa]

It really would be nice. Please, bring it in!
I am using SSH that comes with latest Widows 10:

OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5

and it still is not there :-(

[musm]

Also noted in PowerShell/openssh-portable#463

[musm]

Setting in ~/.ssh/config

ControlMaster auto
ControlPath ~/.ssh/master-%r@%h:%p

Leads to the errors when attempting to connect to any server:

getsockname failed: Bad file descriptor
channel_send_open: channel 0: unexpected internal error

[mcgarrah]

Still getting the error when trying the sockets for multiplexing.

C:\Users\mcgarrah>ssh -V
OpenSSH_for_Windows_7.6p1, LibreSSL 2.6.4

C:\Users\mcgarrah>ssh -S ~/.ssh/control/test  ec2-user@10.196.80.10
getsockname failed: Not a socket

C:\Users\mcgarrah>ssh -vvv -S ~/.ssh/control/test  ec2-user@10.196.80.10
OpenSSH_for_Windows_7.6p1, LibreSSL 2.6.4
debug1: Reading configuration data C:\\Users\\u107250/.ssh/config
debug3: Failed to open file:C:\\ProgramData\\ssh/ssh_config error:2
debug3: w32_getpeername ERROR: not sock :3
debug3: w32_getpeername ERROR: not sock :3
debug1: getpeername failed: Not a socket
debug3: w32_getsockname ERROR: not sock :3
debug3: w32_getsockname ERROR: not sock :3
getsockname failed: Not a socket
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: ssh_packet_send_mux: type 90
debug1: Entering interactive session.
debug1: pledge: network
debug1: console supports the ansi parsing
debug2: client_check_window_change: changed

[mew1033]

Adding this would be amazing. It's the last thing (for me) that windows openssh doesn't have that things like Putty/Kitty do.

[juvieorg]

Hi man, I think that problem is in permission of mutiplex folder. The service account can't create there the socket.
If you add permission for multiplex folder problem solved (add SERVICE_ACCOUNT full control for 'control' folder in your case)
I tested on newer version OpenSSH in windoze - but issue started with same symptoms.
I hope the my note help you.

[solaris-ventus]

It's a pity, a pity. Required functionality

[mew1033]

Here's another ping for ControlMaster functionality. Any updated word on when/if this might be coming? Thanks!

[FlorianDeconinck]

Unreliable information, please disregard

Hi everyone.

Here's a workaround dug from the depth of openssh bug list

Tested on windows 10 2h22 / GitBash
* do your ssh -MNf with ControlMaster and ControlPath in the config unchanged
* then for each mux connection run ssh -O proxy

Does not fix original issue, but gives you mux terminal.

[woodda]

add SERVICE_ACCOUNT full control for 'control' folder in your case

If this indeed is a workaround solution, it would be helpful if you gave step by step instructions for doing the above.

[youk]

@FlorianDeconinck Not clear how it is supposed to work and what you were testing. -O option requires setting ControlPath (-S option). Setting ControlPath makes OpenSSH fail, as it is not supported on Windows (this is what this issue is about).

[FlorianDeconinck]

@FlorianDeconinck Not clear how it is supposed to work and what you were testing. -O option requires setting ControlPath (-S option). Setting ControlPath makes OpenSSH fail, as it is not supported on Windows (this is what this issue is about).

Hey,
I have actually moved on from this setup due too many problems stacking up, so indeed I might be talking out of nothing. I've edited the comment so it's disregarded.

Good luck on the bug hunt.

[youk]

@FlorianDeconinck Thanks. I don't think there is a bug. It's just not implemented. The only bug is that the corresponding command line options are available in the Windows port.

[timon-michel-scopevisio]

Can we get the "feature request" label specified on https://github.com/PowerShell/Win32-OpenSSH/wiki/Project-Scope here? I am afraid this issue might be forgotten because no one labeled it yet

[oladarula]

yeah, it is a pitty that it is not working. Seems the only feature holding me back for production use.