upstream commit

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

Upstream-ID: 943080fe3864715c423bdeb7c920bb30c4eee861

diff --git a/PROTOCOL.mux b/PROTOCOL.mux
index b5832561c0e80464af811aea5bc9fb50c797807a..f042961f1177e0d35aefc798086d57f0fb35ba8d 100644 (file)
--- 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 $