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

SSH port forwarding is now configurable in mid-session. After doing

Browse Source 
Change Settings, the port forwarding setup function is run again,
and tags all existing port forwardings as `do not keep'. Then it
iterates through the config in the normal way; when it encounters a
port forwarding which is already in the tree, it tags it `keep'
rather than setting it up from scratch. Finally, it goes through the
tree and removes any that haven't been labelled `keep'. Hence,
editing the list of forwardings in Change Settings has the effect of
cancelling any forwardings you remove, and adding any new ones.

The SSH panel now appears in the reconfig box, and is empty apart
from a message explaining that it has to be there for subpanels of
it to exist. Better wording for this message would be welcome.

[originally from svn r5030]
This commit is contained in:
Simon Tatham
2004-12-28 14:07:05 +00:00
parent 67f93aa30e
commit 81df0d4253
5 changed files with 375 additions and 158 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
doc/config.but
View File

@ -2399,6 +2399,26 @@ address to listen on, by specifying (for instance) \c{127.0.0.5:79}.
See \k{using-port-forwarding} for more information on how this
works and its restrictions.
You can modify the currently active set of port forwardings in
mid-session using \q{Change Settings}. If you delete a local or
dynamic port forwarding in mid-session, PuTTY will stop listening
for connections on that port, so it can be re-used by another
program. If you delete a remote port forwarding, note that:
\b The SSHv1 protocol contains no mechanism for asking the server to
stop listening on a remote port.
\b The SSHv2 protocol does contain such a mechanism, but not all SSH
servers support it. (In particular, OpenSSH does not support it in
any version earlier than 3.9.)
If you ask to delete a remote port forwarding and PuTTY cannot make
the server actually stop listening on the port, it will instead just
start refusing incoming connections on that port. Therefore,
although the port cannot be reused by another program, you can at
least be reasonably sure that server-side programs can no longer
access the service at your end of the port forwarding.
\S{config-ssh-portfwd-localhost} Controlling the visibility of
forwarded ports