Sunday, June 28, 2020

"getsockname failed: Not a socket" on Windows

New Windows 10 versions come with a Windows port of OpenSSH, so ssh can be done from the Windows command line even outside Bash on Ubuntu on Windows. I tried to set up connection reuse (ControlMaster and ControlPath directives in the SSH configuration), but then found that all connections to my specifed host failed with "getsockname failed: Not a socket." If I understand correctly, OpenSSH is trying to use UNIX sockets to coordinate between ssh processes. Alas, it cannot figure out how to use sockets on Windows. As far as I can tell, SSH connection reuse does not currently work on Windows.

No comments:

Post a Comment