Stop proxying connections to localhost by default; should fix

[u/mdw/putty] / doc / config.but

diff --git a/doc/config.but b/doc/config.but
index 6af3546..dfe7da5 100644 (file)
--- a/doc/config.but
+++ b/doc/config.but
@@ -1,4 +1,4 @@
-\versionid $Id: config.but,v 1.42 2002/09/26 18:37:33 simon Exp $
+\versionid $Id: config.but,v 1.46 2002/12/18 12:18:54 simon Exp $

 
 \C{config} Configuring PuTTY
 
 
 \C{config} Configuring PuTTY
 


@@ -686,6 +686,11 @@ constitute an overload, how short a time period they have to arrive
 in to do so, and how much silent time is required before the
 overload feature will deactivate itself.
 
 in to do so, and how much silent time is required before the
 overload feature will deactivate itself.
 

+Bell overload mode is always deactivated by any keypress in the
+terminal. This means it can respond to large unexpected streams of
+data, but does not interfere with ordinary command-line activities
+that generate beeps (such as filename completion).
+

 \H{config-features} The Features panel
 
 PuTTY's terminal emulation is very highly featured, and can do a lot
 \H{config-features} The Features panel
 
 PuTTY's terminal emulation is very highly featured, and can do a lot


@@ -1434,6 +1439,12 @@ from proxying.
 
 This excludes both of the above ranges at once.
 
 
 This excludes both of the above ranges at once.
 

+Connections to the local host (the host name \c{localhost}, and any
+loopback IP address) are never proxied, even if the proxy exclude
+list does not explicitly contain them. It is very unlikely that this
+behaviour would ever cause problems, but if it does you can change
+it by enabling \q{Consider proxying local host connections}.
+

 \S{config-proxy-auth} Username and password
 
 \cfg{winhelp-topic}{proxy.auth}
 \S{config-proxy-auth} Username and password
 
 \cfg{winhelp-topic}{proxy.auth}


@@ -1449,7 +1460,8 @@ proxies and SOCKS 5 proxies.
 \b SOCKS 4 can use the \q{Username} field, but does not support
 passwords.
 
 \b SOCKS 4 can use the \q{Username} field, but does not support
 passwords.
 

-\b Authentication is meaningless in Telnet proxies.
+\b You can specify a way to include a username and password in the
+Telnet proxy command (see \k{config-proxy-command}).

 
 \S{config-proxy-command} Specifying the Telnet proxy command
 
 
 \S{config-proxy-command} Specifying the Telnet proxy command
 


@@ -1467,8 +1479,20 @@ other character. \c{\\\\} is used to encode the \c{\\} character
 itself.
 
 Also, the special strings \c{%host} and \c{%port} will be replaced
 itself.
 
 Also, the special strings \c{%host} and \c{%port} will be replaced

-by the host name and port number you want to connect to. To get a
-literal \c{%} sign, enter \c{%%}.
+by the host name and port number you want to connect to. The strings
+\c{%user} and \c{%pass} will be replaced by the proxy username and 
+password you specify. To get a literal \c{%} sign, enter \c{%%}.
+
+If the Telnet proxy server prompts for a username and password
+before commands can be sent, you can use a command such as:
+
+\c %user\\n%pass\\nconnect %host %port\\n
+
+This will send your username and password as the first two lines to 
+the proxy, followed by a command to connect to the desired host and 
+port. Note that if you do not include the \c{%user} or \c{%pass}
+tokens in the Telnet command, then the \q{Username} and \q{Password}
+configuration fields will be ignored.

 
 \S{config-proxy-socksver} Selecting the version of the SOCKS protocol
 
 
 \S{config-proxy-socksver} Selecting the version of the SOCKS protocol
 


@@ -1863,6 +1887,19 @@ in the list box.
 To remove a port forwarding, simply select its details in the list
 box, and click the \q{Remove} button.
 
 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
 
 \S{config-ssh-portfwd-localhost} Controlling the visibility of
 forwarded ports