Antonin Brothanek points out that `Incoming packet was garbled on

decryption' could be a result of the wrong setting of the
`Miscomputes SSH2 encryption keys' bug workaround option.

[originally from svn r2751]

diff --git a/doc/errors.but b/doc/errors.but
index 207cd196a2c40541de809282aca9c9b0878f81c7..6c0054d6ee51a1c300faa5628f93ea153b3c36a3 100644 (file)
--- a/doc/errors.but
+++ b/doc/errors.but
@@ -1,4 +1,4 @@
-\versionid $Id: errors.but,v 1.2 2002/11/25 19:02:23 ben Exp $
+\versionid $Id: errors.but,v 1.3 2003/01/30 10:19:05 simon Exp $
 
 \C{errors} Common error messages
 
@@ -151,8 +151,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.
 
-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}