Add another bug workaround, this one for old OpenSSH (<2.3) servers

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

diff --git a/doc/config.but b/doc/config.but
index 37c959c..77a5566 100644 (file)
--- a/doc/config.but
+++ b/doc/config.but
@@ -1,4 +1,4 @@
-\versionid $Id: config.but,v 1.52 2003/01/27 23:03:30 simon Exp $
+\versionid $Id: config.but,v 1.54 2003/02/04 13:02:51 simon Exp $
 
 \C{config} Configuring PuTTY
 
@@ -1497,7 +1497,7 @@ and your SOCKS 4 server cannot deal with it, this might be why.
 If your proxy requires authentication, you can enter a username and
 a password in the \q{Username} and \q{Password} boxes.
 
-Authentication is not supported for all forms of proxy:
+Authentication is not fully supported for all forms of proxy:
 
 \b Username and password authentication is supported for HTTP
 proxies and SOCKS 5 proxies.
@@ -1531,7 +1531,7 @@ 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
+\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 
@@ -2172,6 +2172,24 @@ workaround, you need to enable it manually.
 
 This is an SSH2-specific bug.
 
+\S{config-ssh-bug-pksessid2} \q{Misuses the session ID in PK auth}
+
+\cfg{winhelp-topic}{ssh.bugs.rsapad2}
+
+Versions below 2.3 of OpenSSH require SSH2 public-key authentication
+to be done slightly differently: the data to be signed by the client
+contains the session ID formatted in a different way. If public-key
+authentication mysteriously does not work but the Event Log (see
+\k{using-eventlog}) thinks it has successfully sent a signature, it
+might be worth enabling the workaround for this bug to see if it
+helps.
+
+If this bug is detected, PuTTY will sign data in the way OpenSSH
+expects. If this bug is enabled when talking to a correct server,
+SSH2 public-key authentication will fail.
+
+This is an SSH2-specific bug.
+
 \H{config-file} Storing configuration in a file
 
 PuTTY does not currently support storing its configuration in a file