nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-07-02 03:52:49 -05:00
Code Issues Projects Releases Wiki Activity

Implement `portfwd-loopback-choice'. Works on local side in Unix as

Browse Source 
well, though it's a lot less useful since you still can't bind to
low-numbered ports of odd loopback IPs. Should work in principle for
SSH2 remote forwardings as well as local ones, but OpenSSH seems
unwilling to cooperate.

[originally from svn r2344]
This commit is contained in:
Simon Tatham
2002-12-18 11:39:25 +00:00
parent 8cb52a26e1
commit 99b870dbc6
9 changed files with 182 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
doc/config.but
View File

@ -1,4 +1,4 @@
\versionid $Id: config.but,v 1.44 2002/10/22 09:40:38 simon Exp $
\versionid $Id: config.but,v 1.45 2002/12/18 11:39:25 simon Exp $
\C{config} Configuring PuTTY
@ -1881,6 +1881,19 @@ in the list box.
To remove a port forwarding, simply select its details in the list
box, and click the \q{Remove} button.
In the \q{Source port} box, you can also optionally enter an IP
address to listen on. Typically a Windows machine can be asked to
listen on any single IP address in the \cw{127.*.*.*} range, and all
of these are loopback addresses available only to the local machine.
So if you forward (for example) \c{127.0.0.5:79} to a remote
machine's \cw{finger} port, then you should be able to run commands
such as \c{finger fred@127.0.0.5}. This can be useful if the program
connecting to the forwarded port doesn't allow you to change the
port number it uses. This feature is available for local-to-remote
forwarded ports; SSH1 is unable to support it for remote-to-local
ports, while SSH2 can support it in theory but servers will not
necessarily cooperate.
\S{config-ssh-portfwd-localhost} Controlling the visibility of
forwarded ports