[BACK]Return to PROTOCOL CVS log [TXT][DIR] Up to [local] / src / usr.bin / ssh

Diff for /src/usr.bin/ssh/PROTOCOL between version 1.48 and 1.49

version 1.48, 2022/11/07 01:53:01 version 1.49, 2023/08/28 03:28:43
Line 104 
Line 104 
   
 This is identical to curve25519-sha256 as later published in RFC8731.  This is identical to curve25519-sha256 as later published in RFC8731.
   
   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          "ping@openssh.com"
           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.
   
 2. Connection protocol changes  2. Connection protocol changes
   
 2.1. connection: Channel write close extension "eow@openssh.com"  2.1. connection: Channel write close extension "eow@openssh.com"
Legend:
Removed from v.1.48  
changed lines
  Added in v.1.49