summaryrefslogtreecommitdiffhomepage
path: root/LICENSE
diff options
context:
space:
mode:
authorSteven Noonan <steven@uplinklabs.net>2012-10-15 04:09:33 -0700
committerJeff Forcier <jeff@bitprophet.org>2012-11-05 13:30:48 -0800
commit31ea4f0734a086f2345aaea57fd6fc1c3ea4a87e (patch)
tree095d36d97a64b27a95a610c3c9466a9da06bda85 /LICENSE
parentfd5e29b5a8aff1fe9f11f9f7bee5f0eb85ae569a (diff)
SSHClient: add 'sock' parameter to connect() for tunneling
Re #77 This parameter, if set, can be used to make Paramiko wrap an existing socket connected to a remote SSH server. For instance, you could set up another SSHClient directly connected to a "gateway" host, and then create a direct-tcpip tunnel to a "target" host directly accessible from the gateway's perspective (e.g. think of trying to establish an SSH connection to hosts behind a NAT). The gateway host would then establish a TCP connection to the target host directly, and a channel is exposed on the client side. This channel could be wrapped by an SSHClient class using the connect() function, avoiding the need to establish a new TCP connnection. This effectively allows you to create tunneled SSH connections. Based on work by Oskari Saarenmaa <os@ohmu.fi>, in Paramiko pull request #39. Signed-off-by: Steven Noonan <steven@uplinklabs.net>
Diffstat (limited to 'LICENSE')
0 files changed, 0 insertions, 0 deletions