Tweak language re "Remote ports [accept connections from other hosts]"

[sgt/putty] / doc / using.but

diff --git a/doc/using.but b/doc/using.but
index 2fd341e..3ca6b26 100644 (file)
--- a/doc/using.but
+++ b/doc/using.but
@@ -1,4 +1,4 @@
-\versionid $Id: using.but,v 1.26 2004/07/30 09:38:37 jacob Exp $
+\versionid $Id: using.but,v 1.29 2004/09/16 15:44:58 jacob Exp $
 
 \C{using} Using PuTTY
 
@@ -273,6 +273,8 @@ then PuTTY cannot currently support it. If this is a problem for
 you, you should mail the PuTTY authors \#{FIXME} and give details
 (see \k{feedback}).
 
+For more options relating to X11 forwarding, see \k{config-ssh-x11}.
+
 \H{using-port-forwarding} Using \i{port forwarding} in SSH
 
 The SSH protocol has the ability to forward arbitrary network
@@ -350,7 +352,8 @@ your client PC can connect to the forwarded port.
 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).
+SSH 2 servers honour it (in OpenSSH, for example, it's usually
+disabled by default).
 
 You can also specify an \i{IP address} to listen on. Typically a
 Windows machine can be asked to listen on any single IP address in
@@ -364,6 +367,10 @@ 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.
 
+(Note that if you're using Windows XP Service Pack 2, you may need
+to obtain a fix from Microsoft in order to use addresses like
+\cw{127.0.0.5} - see \k{faq-alternate-localhost}.)
+
 \H{using-rawprot} Making \i{raw TCP connections}
 
 A lot of \I{debugging Internet protocols}Internet protocols are