You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Unix sockets are only forwarded by SSH forwarder. For Windows ssh in use is coming from the subsystem (msys2/cygwin/wsl) and can't communicate with the native AF_UNIX on Windows. This will require some sort of a solution, where this socket from host is connected through STDIO over SSH or TCP with mTLS over SSH. It is theoretically possible to handle it from subsystem Unix socket to native Windows one, but this is complicated by the fact that one of the recommended implementations (known to work well enough) is Git for Windows, which doesn't have straight way to develop custom tools for it (it is not guaranteed to be compatible with msys2, because of the forked nature).
The text was updated successfully, but these errors were encountered:
Description
Currently Unix sockets are only forwarded by SSH forwarder. For Windows ssh in use is coming from the subsystem (msys2/cygwin/wsl) and can't communicate with the native AF_UNIX on Windows. This will require some sort of a solution, where this socket from host is connected through STDIO over SSH or TCP with mTLS over SSH. It is theoretically possible to handle it from subsystem Unix socket to native Windows one, but this is complicated by the fact that one of the recommended implementations (known to work well enough) is Git for Windows, which doesn't have straight way to develop custom tools for it (it is not guaranteed to be compatible with msys2, because of the forked nature).
The text was updated successfully, but these errors were encountered: