[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Server API: How to communicate connection failures to client
[Thread Prev] | [Thread Next]
- Subject: Re: Server API: How to communicate connection failures to client
- From: Stef Bon <stefbon@xxxxxxxxx>
- Reply-to: libssh@xxxxxxxxxx
- Date: Thu, 21 Feb 2019 19:32:49 +0100
- To: libssh@xxxxxxxxxx
- Cc: g4-lisz@xxxxxxxxxxxx
Hi, I've written my own ssh client, and a sftp server. The client can connect to the sftp server via a socket (using direct-streamlocal@xxxxxxxxxxx).Now my client get's a SSH_MSG_CHANNEL_OPEN_FAILURE msg when the sftp server is not running (and thus the local socket is not there)and a SSH_MSG_CHANNEL_EOF when the sftp server is normally running as it should, the connection is made and then is terminated or crashes.You use direct-tcpip, but this is handled the same. Stef
Re: Server API: How to communicate connection failures to client | g4-lisz@xxxxxxxxxxxx |
Server API: How to communicate connection failures to client | g4-lisz@xxxxxxxxxxxx |
Re: Server API: How to communicate connection failures to client | g4-lisz@xxxxxxxxxxxx |
Re: Server API: How to communicate connection failures to client | Andreas Schneider <asn@xxxxxxxxxxxxxx> |