https://bugzilla.mindrot.org/show_bug.cgi?id=3614
--- Comment #6 from Darren Tucker <dtuc...@dtucker.net> ---
(In reply to micet2004-github from comment #5)
> If you agree this feature
> request could be helpful for several users, than the socks way could
> be an easy start for this.
I neglected to mention it in my earlier reply, but this already exists
in the one-argument variant of -R / RemoteForward:
-R [bind_address:]port
Specifies that connections to the given TCP port or Unix
socket
on the remote (server) host are to be forwarded to the
local
side.
This works by allocating a socket to listen to either a
TCP port
or to a Unix socket on the remote side. Whenever a
connection is
made to this port [...] if no explicit destination was
specified, ssh will act as a SOCKS 4/5 proxy and forward
connec-
tions to the destinations requested by the remote SOCKS
client.
It was added in OpenSSH 7.6:https://www.openssh.com/txt/release-7.6
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
