upstream commit

describe magic for setting up Unix domain socket fowards
 via the mux channel; bz#2422 patch from Daniel Black

Upstream-ID: 943080fe3864715c423bdeb7c920bb30c4eee861
This commit is contained in:
djm@openbsd.org 2015-07-17 03:04:27 +00:00 committed by Damien Miller
parent d3e2aee414
commit 356b61f365
1 changed files with 7 additions and 1 deletions

View File

@ -116,6 +116,12 @@ A client may request the master to establish a port forward:
forwarding type may be MUX_FWD_LOCAL, MUX_FWD_REMOTE, MUX_FWD_DYNAMIC. forwarding type may be MUX_FWD_LOCAL, MUX_FWD_REMOTE, MUX_FWD_DYNAMIC.
If listen port is (unsigned int) -2, then the listen host is treated as
a unix socket path name.
If connect port is (unsigned int) -2, then the connect host is treated
as a unix socket path name.
A server may reply with a MUX_S_OK, a MUX_S_REMOTE_PORT, a A server may reply with a MUX_S_OK, a MUX_S_REMOTE_PORT, a
MUX_S_PERMISSION_DENIED or a MUX_S_FAILURE. MUX_S_PERMISSION_DENIED or a MUX_S_FAILURE.
@ -219,4 +225,4 @@ XXX inject packet (what about replies)
XXX server->client error/warning notifications XXX server->client error/warning notifications
XXX send signals via mux XXX send signals via mux
$OpenBSD: PROTOCOL.mux,v 1.9 2012/06/01 00:49:35 djm Exp $ $OpenBSD: PROTOCOL.mux,v 1.10 2015/07/17 03:04:27 djm Exp $