[
https://issues.apache.org/jira/browse/SSHD-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777614#comment-16777614
]
Goldstein Lyor commented on SSHD-782:
-------------------------------------
When implementing consider providing several "null message" options:
* {{SSH_MSG_IGNORE}} - default
* {{SSH_MSG_DEBUG}} with some payload...
> Consider implementing a "reverse" keep-alive mechanism in the server
> --------------------------------------------------------------------
>
> Key: SSHD-782
> URL: https://issues.apache.org/jira/browse/SSHD-782
> Project: MINA SSHD
> Issue Type: Improvement
> Affects Versions: 1.7.0
> Reporter: Goldstein Lyor
> Assignee: Goldstein Lyor
> Priority: Minor
> Labels: keepalive, ssh, sshd
>
> The current code contains only a keep-alive mechanism from clients to
> servers. We should consider implementing a "reverse" keep-alive mechanism
> from servers to clients using {{SSH_MSG_IGNORE}} messages. This mechanism
> should be along the lines of the {{Client/ServerAliveInterval}} and
> {{Client/ServerAliveCountMax}} parameters described in
> [sshd_config|https://linux.die.net/man/5/sshd_config] and/or[How to Keep
> Alive SSH
> Sessions|https://patrickmn.com/aside/how-to-keep-alive-ssh-sessions/] The
> mechanism can be used to avoid read timeout on the *client* side (e.g.
> SSHD-781)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
