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

Diff for /src/usr.bin/ssh/PROTOCOL.mux between version 1.2 and 1.3

version 1.2, 2010/05/16 12:55:51 version 1.3, 2011/01/13 21:55:25
Line 28 
Line 28 
 To open a new multiplexed session, a client may send the following  To open a new multiplexed session, a client may send the following
 request:  request:
   
         uint32  MUX_C_MSG_NEW_SESSION          uint32  MUX_C_NEW_SESSION
         uint32  request id          uint32  request id
         string  reserved          string  reserved
         bool    want tty flag          bool    want tty flag
Line 99 
Line 99 
   
 A client may request the master to establish a port forward:  A client may request the master to establish a port forward:
   
         uint32  MUX_C_OPEN_FORWARD          uint32  MUX_C_OPEN_FWD
         uint32  request id          uint32  request id
         uint32  forwarding type          uint32  forwarding type
         string  listen host          string  listen host
Line 118 
Line 118 
         uint32  client request id          uint32  client request id
         uint32  allocated remote listen port          uint32  allocated remote listen port
   
 5. Requesting closure of port forwards  6. Requesting closure of port forwards
   
   Note: currently unimplemented (server will always reply with MUX_S_FAILURE).
   
 A client may request the master to establish a port forward:  A client may request the master to establish a port forward:
   
         uint32  MUX_C_OPEN_FORWARD          uint32  MUX_C_CLOSE_FWD
         uint32  request id          uint32  request id
         uint32  forwarding type  
         string  listen host          string  listen host
         string  listen port          string  listen port
         string  connect host          string  connect host
         string  connect port          string  connect port
   
 forwarding type may be MUX_FWD_LOCAL, MUX_FWD_REMOTE, MUX_FWD_DYNAMIC.  
   
 A server may reply with a MUX_S_OK, a MUX_S_PERMISSION_DENIED or a  A server may reply with a MUX_S_OK, a MUX_S_PERMISSION_DENIED or a
 MUX_S_FAILURE.  MUX_S_FAILURE.
   
 6. Requesting stdio forwarding  7. Requesting stdio forwarding
   
 A client may request the master to establish a stdio forwarding:  A client may request the master to establish a stdio forwarding:
   
Line 153 
Line 152 
 A server may reply with a MUX_S_SESSION_OPEED, a MUX_S_PERMISSION_DENIED  A server may reply with a MUX_S_SESSION_OPEED, a MUX_S_PERMISSION_DENIED
 or a MUX_S_FAILURE.  or a MUX_S_FAILURE.
   
 7. Status messages  8. Status messages
   
 The MUX_S_OK message is empty:  The MUX_S_OK message is empty:
   
Line 170 
Line 169 
         uint32  client request id          uint32  client request id
         string  reason          string  reason
   
 7. Protocol numbers  9. Protocol numbers
   
 #define MUX_MSG_HELLO           0x00000001  #define MUX_MSG_HELLO           0x00000001
 #define MUX_C_NEW_SESSION       0x10000002  #define MUX_C_NEW_SESSION       0x10000002
 #define MUX_C_ALIVE_CHECK       0x10000004  #define MUX_C_ALIVE_CHECK       0x10000004
 #define MUX_C_TERMINATE         0x10000005  #define MUX_C_TERMINATE         0x10000005
 #define MUX_C_OPEN_FORWARD      0x10000006  #define MUX_C_OPEN_FWD          0x10000006
 #define MUX_C_CLOSE_FORWARD     0x10000007  #define MUX_C_CLOSE_FWD         0x10000007
   #define MUX_C_NEW_STDIO_FWD     0x10000008
 #define MUX_S_OK                0x80000001  #define MUX_S_OK                0x80000001
 #define MUX_S_PERMISSION_DENIED 0x80000002  #define MUX_S_PERMISSION_DENIED 0x80000002
 #define MUX_S_FAILURE           0x80000003  #define MUX_S_FAILURE           0x80000003
Legend:
Removed from v.1.2  
changed lines
  Added in v.1.3