Re: Server API: How to communicate connection failures to client

[g4-lisz@xxxxxxxxxxxx]

On 22.02.19 01:15, g4-lisz@xxxxxxxxxxxx wrote:

> On 21.02.19 19:32, Stef Bon wrote:
>
>> 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
> Hi Stef and thanks for your answer!
>
> Sending this message is also my conclusion after reading the RFC,
> although it's not really clear there IMHO.
>
> How did you manage to send SSH_MSG_CHANNEL_OPEN_FAILURE using libssh? Or
> you wrote your server on your own from scratch?

I can't find any exposed function to send other messages than
SSH2_MSG_UNIMPLEMENTED (through ssh_message_reply_default).

So this needed a patch...

Till