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

[sgt/putty] / doc / errors.but

diff --git a/doc/errors.but b/doc/errors.but
index 0c3e211..51786b9 100644 (file)
--- a/doc/errors.but
+++ b/doc/errors.but
@@ -1,4 +1,4 @@
-\versionid $Id: errors.but,v 1.1 2002/10/01 16:27:36 simon Exp $
+\versionid $Id: errors.but,v 1.4 2003/01/31 23:18:44 ben Exp $

 
 \C{errors} Common error messages
 
 
 \C{errors} Common error messages
 


@@ -73,6 +73,18 @@ have configured PuTTY to consider strong enough.
 
 See \k{config-ssh-encryption} for more information on this message.
 
 
 See \k{config-ssh-encryption} for more information on this message.
 

+\H{errors-toomanyauth} \q{Server sent disconnect message type 2
+(SSH_DISCONNECT_PROTOCOL_ERROR): "Too many authentication failures for root"}
+
+This message is produced by an OpenSSH (or Sun SSH) server if it
+receives more failed authentication attempts than it is willing to
+tolerate.  This can easily happen if you are using Pageant and have a
+large number of keys loaded into it.  This can be worked around on the
+server by disabling public-key authentication or (for Sun SSH only) by
+increasing \c{MaxAuthTries} in \c{sshd_config}.  Neither of these is a
+really satisfactory solution, and we hope to provide a better one in a
+future version of PuTTY.
+

 \H{errors-memory} \q{Out of memory}
 
 This occurs when PuTTY tries to allocate more memory than the system
 \H{errors-memory} \q{Out of memory}
 
 This occurs when PuTTY tries to allocate more memory than the system


@@ -93,7 +105,7 @@ memory} error.
 
 This can happen in SSH 2, if PuTTY and the server have not enabled
 encryption in the same way (see \k{faq-outofmem} in the FAQ). Some
 
 This can happen in SSH 2, if PuTTY and the server have not enabled
 encryption in the same way (see \k{faq-outofmem} in the FAQ). Some

-versions of OpenSSH have a knownq problem with this: see
+versions of OpenSSH have a known problem with this: see

 \k{faq-openssh-bad-openssl}.
 
 This can also happen in PSCP or PSFTP, if your login scripts on the
 \k{faq-openssh-bad-openssl}.
 
 This can also happen in PSCP or PSFTP, if your login scripts on the


@@ -151,8 +163,12 @@ gone wrong in the encryption or decryption process. It's difficult
 to tell from this error message whether the problem is in the client
 or in the server.
 
 to tell from this error message whether the problem is in the client
 or in the server.
 

-A known server problem which can cause this error is described in
-\k{faq-openssh-bad-openssl} in the FAQ.
+If you get this error, one thing you could try would be to fiddle
+with the setting of \q{Miscomputes SSH2 encryption keys} on the Bugs
+panel (see \k{config-ssh-bug-derivekey2}).
+
+Another known server problem which can cause this error is described
+in \k{faq-openssh-bad-openssl} in the FAQ.

 
 \H{errors-x11-proxy} \q{Authentication failed at PuTTY X11 proxy}
 
 
 \H{errors-x11-proxy} \q{Authentication failed at PuTTY X11 proxy}