[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.7 and 1.8

version 1.7, 2008/06/12 05:15:41 version 1.8, 2008/06/28 07:25:07
Line 86 
Line 86 
   
 5. connection: Tunnel forward extension "tun@openssh.com"  5. connection: Tunnel forward extension "tun@openssh.com"
   
 OpenSSH supports layer 2 and layer 3 tunneling via the "tun@openssh.com"  OpenSSH supports layer 2 and layer 3 tunnelling via the "tun@openssh.com"
 channel type. This channel type supports forwarding of network packets  channel type. This channel type supports forwarding of network packets
 with datagram boundaries entact between endpoints equipped with  with datagram boundaries intact between endpoints equipped with
 interfaces like the BSD tun(4) device. Tunnel forwarding channels are  interfaces like the BSD tun(4) device. Tunnel forwarding channels are
 requested by the client with the following packet:  requested by the client with the following packet:
   
Line 142 
Line 142 
         uint32                  packet length          uint32                  packet length
         byte[packet length]     frame          byte[packet length]     frame
   
 The "frame" field contains an IEEE 802.3 ethernet frame, including  The "frame" field contains an IEEE 802.3 Ethernet frame, including
 header.  header.
   
 6. sftp: Reversal of arguments to SSH_FXP_SYMLINK  6. sftp: Reversal of arguments to SSH_FXP_SYMLINK
   
 When OpenSSH's sftp-server was implemented, the order of the arguments  When OpenSSH's sftp-server was implemented, the order of the arguments
 to the SSH_FXP_SYMLINK method was inadvertendly reversed. Unfortunately,  to the SSH_FXP_SYMLINK method was inadvertently reversed. Unfortunately,
 the reversal was not noticed until the server was widely deployed. Since  the reversal was not noticed until the server was widely deployed. Since
 fixing this to follow the specification would cause incompatibility, the  fixing this to follow the specification would cause incompatibility, the
 current order was retained. For correct operation, clients should send  current order was retained. For correct operation, clients should send
Line 177 
Line 177 
 string, e.g. "1". The version will be incremented if the extension is  string, e.g. "1". The version will be incremented if the extension is
 ever changed in an incompatible way. The server MAY advertise the same  ever changed in an incompatible way. The server MAY advertise the same
 extension with multiple versions (though this is unlikely). Clients MUST  extension with multiple versions (though this is unlikely). Clients MUST
 check the version number before attemping to use the extension.  check the version number before attempting to use the extension.
   
 8. sftp: Extension request "posix-rename@openssh.com"  8. sftp: Extension request "posix-rename@openssh.com"
   
Line 207 
Line 207 
         string          "statvfs@openssh.com"          string          "statvfs@openssh.com"
         string          path          string          path
   
 The "fstatvfs@openssh.com" operates on an open filehandle:  The "fstatvfs@openssh.com" operates on an open file handle:
   
         uint32          id          uint32          id
         string          "fstatvfs@openssh.com"          string          "fstatvfs@openssh.com"

Legend:
Removed from v.1.7  
changed lines
  Added in v.1.8