summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authordjm <djm@openbsd.org>2015-07-17 03:04:27 +0000
committerdjm <djm@openbsd.org>2015-07-17 03:04:27 +0000
commita6f3afedb40d8c700e493dec770d11f5a858f092 (patch)
tree480b2cfd4b875568d5f06bba66c04b795840ce75
parentfix incorrect test for SSH1 keys when compiled without SSH1 support (diff)
downloadwireguard-openbsd-a6f3afedb40d8c700e493dec770d11f5a858f092.tar.xz
wireguard-openbsd-a6f3afedb40d8c700e493dec770d11f5a858f092.zip
describe magic for setting up Unix domain socket fowards via
the mux channel; bz#2422 patch from Daniel Black
-rw-r--r--usr.bin/ssh/PROTOCOL.mux8
1 files changed, 7 insertions, 1 deletions
diff --git a/usr.bin/ssh/PROTOCOL.mux b/usr.bin/ssh/PROTOCOL.mux
index b5832561c0e..f042961f117 100644
--- a/usr.bin/ssh/PROTOCOL.mux
+++ b/usr.bin/ssh/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 $