Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • Yes this. You have "Foo over SOCKS over TCP" between the client and the SSH client ; "Foo over SSH over TCP" between the SSH client and the SSH server ; "Foo over TCP" between the SSH server and the target server. The SSH client multiplexes all the incoming connections over the same SSH connection. Commented Feb 7, 2019 at 20:52
  • @ysdx I believe SOCKS is connection-less, once the forward target has been told, the originator begins to directly speak any application layer protocol. There is no xxx-over-SOCKS Commented Feb 8, 2019 at 15:11
  • 炸鱼薯条德里克, well it's "foo over SOCKS" in the sense that the initial bits of the communication is the SOCKS "handhsake". After that is done there is no more bits of SOCKS protocol involved in the stream. I would not call SOCKS "connection-less" however. Commented Feb 10, 2019 at 10:33
  • i.e. SOCKS is completely implemented by the SSH client (there is ne special support in the server) by using the standard SSH commands. If your OpenSSH client implements SOCKS support it should be able to do it with any compliant SSH server (provided TCP fowarding is allowed in the server). Commented Feb 10, 2019 at 10:36