version 1.15, 2016/05/03 09:03:49 |
version 1.16, 2017/04/30 23:26:54 |
|
|
*/ |
*/ |
|
|
/* |
/* |
* SSH1: |
* The tty mode description is a string, consisting of |
* The tty mode description is a stream of bytes. The stream consists of |
|
* opcode-arguments pairs. It is terminated by opcode TTY_OP_END (0). |
* opcode-arguments pairs. It is terminated by opcode TTY_OP_END (0). |
* Opcodes 1-127 have one-byte arguments. Opcodes 128-159 have integer |
* Opcodes 1-159 have uint32 arguments. |
* arguments. Opcodes 160-255 are not yet defined, and cause parsing to |
* Opcodes 160-255 are not yet defined and cause parsing to stop (they |
* stop (they should only be used after any other data). |
* should only be used after any other data). |
* |
* |
* SSH2: |
* The client puts in the string any modes it knows about, and the |
* Differences between SSH1 and SSH2 terminal mode encoding include: |
|
* 1. Encoded terminal modes are represented as a string, and a stream |
|
* of bytes within that string. |
|
* 2. Opcode arguments are uint32 (1-159); 160-255 remain undefined. |
|
* 3. The values for TTY_OP_ISPEED and TTY_OP_OSPEED are different; |
|
* 128 and 129 vs. 192 and 193 respectively. |
|
* |
|
* The client puts in the stream any modes it knows about, and the |
|
* server ignores any modes it does not know about. This allows some degree |
* server ignores any modes it does not know about. This allows some degree |
* of machine-independence, at least between systems that use a posix-like |
* of machine-independence, at least between systems that use a posix-like |
* tty interface. The protocol can support other systems as well, but might |
* tty interface. The protocol can support other systems as well, but might |