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

Add the remote counterpart for the `local port forwardings accept

Browse Source 
connections from outside localhost' switch. Interestingly OpenSSH
3.0 appears to ignore this (though I know it works because ssh.com
3.0 gets it right, and the SSH packet dump agrees that I'm doing the
right thing).

[originally from svn r1496]
This commit is contained in:
Simon Tatham
2001-12-15 12:15:24 +00:00
parent f10f7c966a
commit 88a3baa065
6 changed files with 69 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
doc/config.but
View File

@ -1,4 +1,4 @@
\versionid $Id: config.but,v 1.21 2001/12/14 14:57:50 simon Exp $
\versionid $Id: config.but,v 1.22 2001/12/15 12:15:24 simon Exp $
\C{config} Configuring PuTTY
@ -1576,6 +1576,27 @@ in the list box.
To remove a port forwarding, simply select its details in the list
box, and click the \q{Remove} button.
\S{config-ssh-portfwd-localhost} Controlling the visibility of
forwarded ports
\cfg{winhelp-topic}{ssh.tunnels.portfwd.localhost}
The source port for a forwarded connection usually does not accept
connections from any machine except the SSH client or server machine
itself (for local and remote forwardings respectively). There are
controls in the Tunnels panel to change this:
\b The \q{Local ports accept connections from other hosts} option
allows you to set up local-to-remote port forwardings in such a way
that machines other than your client PC can connect to the forwarded
port.
\b The \q{Remote ports do the same} option does the same thing for
remote-to-local port forwardings (so that machines other than the
SSH server machine can connect to the forwarded port.) Note that
this feature is only available in the SSH 2 protocol, and not all
SSH 2 servers support it (OpenSSH 3.0 does not, for example).
\H{config-file} Storing configuration in a file
PuTTY does not currently support storing its configuration in a file

18
doc/using.but
View File

@ -1,4 +1,4 @@
\versionid $Id: using.but,v 1.4 2001/12/13 17:38:59 simon Exp $
\versionid $Id: using.but,v 1.5 2001/12/15 12:15:24 simon Exp $
\C{using} Using PuTTY
@ -291,6 +291,22 @@ To do this, just select the \q{Remote} radio button instead of the
number on the \e{server} (note that most servers will not allow you
to use port numbers under 1024 for this purpose).
The source port for a forwarded connection usually does not accept
connections from any machine except the SSH client or server machine
itself (for local and remote forwardings respectively). There are
controls in the Tunnels panel to change this:
\b The \q{Local ports accept connections from other hosts} option
allows you to set up local-to-remote port forwardings in such a way
that machines other than your client PC can connect to the forwarded
port.
\b The \q{Remote ports do the same} option does the same thing for
remote-to-local port forwardings (so that machines other than the
SSH server machine can connect to the forwarded port.) Note that
this feature is only available in the SSH 2 protocol, and not all
SSH 2 servers support it (OpenSSH 3.0 does not, for example).
\H{using-rawprot} Making raw TCP connections
A lot of Internet protocols are composed of commands and responses