Lines Matching +full:protocol +full:- +full:id

1 This document describes the multiplexing protocol used by ssh(1)'s
2 ControlMaster connection-sharing.
7 simple packetised protocol, where each message is proceeded with
14 Most messages from the client to the server contain a "request id"
15 field. This field is returned in replies as "client request id" to
37 the multiplexing protocol and start proxying SSH connection protocol
39 speak a significant subset of the SSH protocol, but in return is able
40 to access basically the full suite of connection protocol features.
52 	uint32  protocol version
57 The current version of the mux protocol is 4. A client should refuse
58 to connect to a master that speaks an unsupported protocol version.
69 	uint32  request id
93 	uint32	client request id
94 	uint32	session id
105 	uint32	session id
109 non-multiplexed ssh(1) connection. Two additional cases that the
118 	uint32	session id
120 3. Requesting passenger-mode stdio forwarding
125 	uint32	request id
143 	uint32	request id
148 	uint32	client request id
156 	uint32	request id
165 	uint32	request id
174 If listen port is (unsigned int) -2, then the listen host is treated as
177 If connect port is (unsigned int) -2, then the connect host is treated
186 	uint32	client request id
194 	uint32	request id
210 	uint32	request id
221 	uint32	request id
227 	uint32	request id
235 	byte[packet length - 2] ...
247 	uint32	client request id
252 	uint32	client request id
256 	uint32	client request id
259 11. Protocol numbers
287 XXX server->client error/warning notifications
290 XXX extensions for multi-agent
291 XXX extensions for multi-X11
296 $OpenBSD: PROTOCOL.mux,v 1.14 2024/01/08 05:11:18 djm Exp $