yang
October 16, 2018, 2:51am
2
SSH Proxy creates a SOCKS proxy for you, and in Core Tunnel we name it Dynamic Port Forwarding . So in Core Tunnel, just create a tunnel and make sure there is a Dynamic Port Forwarding item, set the port number same to the "Listening Port" in SSH Proxy.
Please refer to Dynamic Port Forwarding section in this article:
Introduction
Port forwarding via SSH (SSH tunneling) creates a secure connection between a local computer and a remote machine through which services can be relayed. Because the connection is encrypted, SSH tunneling is useful for transmitting information that uses an unencrypted protocol, such as IMAP, VNC, or IRC.
Types of Port Forwarding
SSH's port forwarding feature can smuggle various types of Internet traffic into or out of a network. This can be used to avoid network monitoring or sni…
And if you have to work with ProxyCommand, there is a howto for it:
It is possible to make a tunnel over a SOCKS or HTTPS proxy, the option for this feature is ProxyCommand . This option is useful if you work behind a draconian firewall and can't establishing ssh connection directly.
Core Tunnel can call the command specified by ProxyCommand, expecting it to make the connection to the proxy server. After the connection is made, Core Tunnel uses the connection as the pipeline, and connects to the remote ssh host through the pipeline.
netcat is one of ProxyComman…
Moreover, Core Tunnel can read your ssh_config:
By default, Core Tunnel uses configuration files in its own container folder:
# known_hosts
~/Library/Group Containers/E78WKS7W4U.io.coressh.ssh/.ssh/known_hosts
# ssh_config
~/Library/Group Containers/E78WKS7W4U.io.coressh.ssh/.ssh/config
This works very well in most of cases. But if you have a lengthy ~/.ssh/config or /etc/ssh/ssh_config, or have StrictHostKeyChecking set to yes and use ~/.ssh/known_hosts, /etc/ssh/ssh_known_hosts as the only source data trusted host keys, you may want to u…
It's much powerful than SSH Proxy, except the lack of traffic routing.