summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authordjm@openbsd.org <djm@openbsd.org>2015-07-17 03:04:27 +0000
committerDamien Miller <djm@mindrot.org>2015-07-17 13:36:29 +1000
commit356b61f365405b5257f5b2ab446e5d7bd33a7b52 (patch)
treeb84bc83d14d3973f8c9d88647df642b2a3421cd5
parentd3e2aee41487d55b8d7d40f538b84ff1db7989bc (diff)
upstream commit
describe magic for setting up Unix domain socket fowards via the mux channel; bz#2422 patch from Daniel Black Upstream-ID: 943080fe3864715c423bdeb7c920bb30c4eee861
-rw-r--r--PROTOCOL.mux8
1 files changed, 7 insertions, 1 deletions
diff --git a/PROTOCOL.mux b/PROTOCOL.mux
index b5832561..f042961f 100644
--- a/PROTOCOL.mux
+++ b/PROTOCOL.mux
@@ -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.
+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
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 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 $