Hello,

while I experimented with ssh I noticed that -D supports using Unix
sockets but this is undocumented in the manpage.

I have no experience about bug/patch submitting upstream, so I'm just
reporting here with a patch. Feel free to forward accordingly.

Best regards
Uwe
The option -D supports (similar to -L) to use a named Unix socket
instead of binding to a port. Add this feature to the manpage.
---
 ssh.1 | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/ssh.1 b/ssh.1
index ad48fc8c816a..f67ee14d12f1 100644
--- a/ssh.1
+++ b/ssh.1
@@ -46,7 +46,7 @@
 .Op Fl B Ar bind_interface
 .Op Fl b Ar bind_address
 .Op Fl c Ar cipher_spec
-.Op Fl D Oo Ar bind_address : Oc Ns Ar port
+.Op Fl D Ar socketspec
 .Op Fl E Ar log_file
 .Op Fl e Ar escape_char
 .Op Fl F Ar configfile
@@ -173,14 +173,21 @@ for more information.
 .Ar port
 .Sm on
 .Xc
+.It Fl D Xo
+.Sm off
+.Ar local_socket
+.Sm on
+.Xc
 Specifies a local
 .Dq dynamic
 application-level port forwarding.
 This works by allocating a socket to listen to
 .Ar port
 on the local side, optionally bound to the specified
-.Ar bind_address .
-Whenever a connection is made to this port, the
+.Ar bind_address
+or the specified Unix socket
+.Ar local_socket .
+Whenever a connection is made to this socket, the
 connection is forwarded over the secure channel, and the application
 protocol is then used to determine where to connect to from the
 remote machine.
-- 
2.29.2