gnodet opened a new issue, #563: URL: https://github.com/apache/mina-sshd/issues/563
### Description See https://github.com/openssh/openssh-portable/blob/V_9_8/PROTOCOL#L107-L138 > 1.9 transport: ping facility > > OpenSSH implements a transport level ping message `SSH2_MSG_PING` > and a corresponding `SSH2_MSG_PONG` reply. > > `#define SSH2_MSG_PING 192` > `#define SSH2_MSG_PONG 193` > > The ping message is simply: > > ` byte SSH_MSG_PING` > ` string data` > > The reply copies the data (which may be the empty string) from the > ping: > > ` byte SSH_MSG_PONG` > ` string data` > > Replies are sent in order. They are sent immediately except when rekeying > is in progress, in which case they are queued until rekeying completes. > > The server advertises support for these messages using the > `SSH2_MSG_EXT_INFO` mechanism (RFC8308), with the following message: > > ` string "[email protected]"` > ` string "0" (version)` > > The ping/reply message is implemented at the transport layer rather > than as a named global or channel request to allow pings with very > short packet lengths, which would not be possible with other > approaches. ### Motivation When this extension is supported by the server, ping messages are sent by the OpenSSH client to perform keystroke timing obfuscation. ### Alternatives considered _No response_ ### Additional context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
