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, an ssh connection failure is not communicated properly to libssh, which means that failed connections simply have to timeout within libssh (only 10 seconds, but still).
This is due to the fact that the socket is non-blocking, which requires getsockopt() to communicate the disposition of the connection, which has not been implemented.
See man connect and search for EINPROGRESS for details.
The text was updated successfully, but these errors were encountered:
Currently, an ssh connection failure is not communicated properly to libssh, which means that failed connections simply have to timeout within libssh (only 10 seconds, but still).
This is due to the fact that the socket is non-blocking, which requires getsockopt() to communicate the disposition of the connection, which has not been implemented.
See
man connect
and search forEINPROGRESS
for details.The text was updated successfully, but these errors were encountered: