It's 2002. Update copyright statements :-)

[sgt/putty] / doc / config.but

diff --git a/doc/config.but b/doc/config.but
index 4d848ef..cb7eb66 100644 (file)
--- a/doc/config.but
+++ b/doc/config.but
@@ -1,4 +1,4 @@
-\versionid $Id: config.but,v 1.18 2001/12/06 20:05:39 simon Exp $
+\versionid $Id: config.but,v 1.25 2002/02/04 13:18:54 simon Exp $

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


@@ -136,6 +136,14 @@ can record everything that went to the terminal, so that someone
 else can replay the session later in slow motion and watch to see
 what went wrong.
 
 else can replay the session later in slow motion and watch to see
 what went wrong.
 

+\b \q{Log SSH packet data}. In this mode (which is only used by SSH
+connections), the SSH message packets sent over the encrypted
+connection are written to the log file. You might need this to debug
+a network-level problem, or more likely to send to the PuTTY authors
+as part of a bug report. \e{BE WARNED} that if you log in using a
+password, the password will appear in the log file, so be sure to
+edit it out before sending the log file to anyone else!
+

 \S{config-logfilename} \q{Log file name}
 
 \cfg{winhelp-topic}{logging.filename}
 \S{config-logfilename} \q{Log file name}
 
 \cfg{winhelp-topic}{logging.filename}


@@ -322,6 +330,11 @@ multiple times at the keyboard. If you set the answerback string to
 be empty, this problem should go away, but doing so might cause
 other problems.
 
 be empty, this problem should go away, but doing so might cause
 other problems.
 

+Note that this is \e{not} the feature of PuTTY which the server will
+typically use to determine your terminal type. That feature is the
+\q{Terminal-type string} in the Connection panel; see
+\k{config-termtype} for details.
+

 \S{config-localecho} \q{Local echo}
 
 \cfg{winhelp-topic}{terminal.localecho}
 \S{config-localecho} \q{Local echo}
 
 \cfg{winhelp-topic}{terminal.localecho}


@@ -1285,6 +1298,22 @@ the Telnet special backspace code, and Control-C will send the
 Telnet special interrupt code. You probably shouldn't enable this
 unless you know what you're doing.
 
 Telnet special interrupt code. You probably shouldn't enable this
 unless you know what you're doing.
 

+\S{config-telnetnl} \q{Return key sends telnet New Line instead of ^M}
+
+\cfg{winhelp-topic}{telnet.newline}
+
+Unlike most other remote login protocols, the Telnet protocol has a
+special \q{new line} code that is not the same as the usual line
+endings of Control-M or Control-J. By default, PuTTY sends the
+Telnet New Line code when you press Return, instead of sending
+Control-M as it does in most other protocols.
+
+Most Unix-style Telnet servers don't mind whether they receive
+Telnet New Line or Control-M; some servers do expect New Line, and
+some servers prefer to see ^M. If you are seeing surprising
+behaviour when you press Return in a Telnet session, you might try
+turning this option off to see if it helps.
+

 \H{config-rlogin} The Rlogin panel
 
 The Rlogin panel allows you to configure options that only apply to
 \H{config-rlogin} The Rlogin panel
 
 The Rlogin panel allows you to configure options that only apply to


@@ -1452,7 +1481,7 @@ your server supports this, you should talk to your system
 administrator about precisely what form these challenges and
 responses take.
 
 administrator about precisely what form these challenges and
 responses take.
 

-\S{config-ssh-tis} \q{Attempt keyboard-interactive authentication}
+\S{config-ssh-ki} \q{Attempt keyboard-interactive authentication}

 
 \cfg{winhelp-topic}{ssh.auth.ki}
 
 
 \cfg{winhelp-topic}{ssh.auth.ki}
 


@@ -1479,6 +1508,28 @@ See \k{pageant} for general information on Pageant, and
 there is a security risk involved with enabling this option; see
 \k{pageant-security} for details.
 
 there is a security risk involved with enabling this option; see
 \k{pageant-security} for details.
 

+\S{config-ssh-changeuser} \q{Allow attempted changes of username in SSH2}
+
+\cfg{winhelp-topic}{ssh.auth.changeuser}
+
+In the SSH 1 protocol, it is impossible to change username after
+failing to authenticate. So if you mis-type your username at the
+PuTTY \q{login as:} prompt, you will not be able to change it except
+by restarting PuTTY.
+
+The SSH 2 protocol \e{does} allow changes of username, in principle,
+but does not make it mandatory for SSH 2 servers to accept them. In
+particular, OpenSSH does not accept a change of username; once you
+have sent one username, it will reject attempts to try to
+authenticate as another user. (Depending on the version of OpenSSH,
+it may quietly return failure for all login attempts, or it may send
+an error message.)
+
+For this reason, PuTTY will by default not prompt you for your
+username more than once, in case the server complains. If you know
+your server can cope with it, you can enable the \q{Allow attempted
+changes of username} option to modify PuTTY's behaviour.
+

 \S{config-ssh-privkey} \q{Private key file for authentication}
 
 \cfg{winhelp-topic}{ssh.auth.privkey}
 \S{config-ssh-privkey} \q{Private key file for authentication}
 
 \cfg{winhelp-topic}{ssh.auth.privkey}


@@ -1546,6 +1597,27 @@ 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.
 

+\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
 \H{config-file} Storing configuration in a file
 
 PuTTY does not currently support storing its configuration in a file