Hi Jakub, right, I have not noticed the function before, thanks. However, I am not sure the API is suitable. What is the general behavior, meaning what happens if a reply is not sent back? Is the connection automatically disconnected? Is it possible to use custom max probes (how many keep-alive packets are sent unsuccessfully before a connection is considered dead) and probe interval (the interval between keep-alive packets) or some specific values are always used? There is no documentation, that is why I am asking. Thanks for providing these details.
Regards, Michal On Friday, March 6, 2020 11:29 CET, Jakub Jelen <[email protected]> wrote: > On Fri, 2020-03-06 at 09:11 +0100, Michal Vaško wrote: > > Hello, > > I was wondering if the authors of libssh would have anything against > > making ssh_global_request() function from channels.h public. It would > > enable implementing NETCONF Call Home SSH keep-alive [1]. Thanks. > > Hello, > in server side, there is already API for sending keepalive messages: > > https://gitlab.com/libssh/libssh-mirror/-/blob/master/include/libssh/server.h#L368 > > In the connection, only one of the peers needs to send the keepalive > messages to keep a connection alive. > > If you need the similar functionality in the client, I would rather see > it implemented by creating a new API function than exposing this > internal function. > > Regards, > -- > Jakub Jelen > Senior Software Engineer > Security Technologies > Red Hat, Inc. > >
