Support all types of SSH tunnels #22
Comments
|
Thanks, @dschep! Also thanks for providing feedback. We definitively want to support more types of tunnels. I see other people requesting that in the Hacker News thread too: https://news.ycombinator.com/item?id=18236125#18240124 |
davrodpin
pushed a commit
that referenced
this issue
Aug 9, 2020
This change adds support for a new type of ssh tunnel, the [remote port forwarding](https://www.ssh.com/ssh/tunneling/example#remote-forwarding). Partially implements #22.
davrodpin
pushed a commit
that referenced
this issue
Aug 9, 2020
This change adds support for a new type of ssh tunnel, the [remote port forwarding](https://www.ssh.com/ssh/tunneling/example#remote-forwarding). Other significant changes: * Adds a new TunnelType attribute to TunnelFlags so it can be passed to the Tunnel object, preparing it to support different types of port forwarding It also improves the description of `start local` command. * Hides how the `SSHChannel` objects are built under `tunnel.New`, opening room to create either ssh `local` or `remote` forwarding tunnels * Adds support for reading `RemoteForward` configuration from the ssh configuration file * Extends the ssh server implementation using for tests to handle "tcpip-forward" requests Partially implements #22.
|
Closing this one. Remote Port Forwarding was implemented o b4239d and I've created a new issue for Dynamic Port Forwarding, #118 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Interesting tool @davrodpin!
I'd expect a tool for managing SSH tunnels to support reverse (
ssh -R) and dynamic (ssh -D) tunnels.Reverse tunnels could be implemented by a
-reverseflag that causes ssh to be spawned with-Rinstead of-L.Dynamic tunnels could be implemented by a
-dynamicflag with makes mole not need(in fact should error if it is present) the-remoteflag.The text was updated successfully, but these errors were encountered: