X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=doc%2Ferrors.but;h=06c247c01e4c465ac35c2f4659b0af9aa5fa5546;hb=3d466aec90909db75eef8b6aaeedcd56eb925a2a;hp=5a0d83dc966d31ab24c1cf5dfc4d914316506c7d;hpb=187d481d735e13f2a45e3ff8d7e3c49df3257116;p=PuTTY.git

diff --git a/doc/errors.but b/doc/errors.but
index 5a0d83dc..06c247c0 100644
--- a/doc/errors.but
+++ b/doc/errors.but
@@ -69,6 +69,9 @@ We need to fix this (fixed-size buffers are almost always a mistake)
 but we haven't got round to it. If you actually have trouble with
 this, let us know and we'll move it up our priority list.
 
+If you're running into this limit, you may want to consider using
+dynamic port forwarding instead; see \k{using-port-forwarding}.
+
 \H{errors-cipher-warning} \q{The first cipher supported by the server is
 ... below the configured warning threshold}
 
@@ -182,6 +185,9 @@ user's home directory on the server. Also, read the PuTTY Event Log;
 the server may have sent diagnostic messages explaining exactly what
 problem it had with your setup.
 
+\K{pubkey-gettingready} has some hints on server-side public key
+setup.
+
 \H{errors-access-denied} \q{Access denied}, \q{Authentication refused}
 
 Various forms of this error are printed in the PuTTY window, or
@@ -235,9 +241,10 @@ gone wrong in the encryption or decryption process. It's difficult
 to tell from this error message whether the problem is in the client,
 in the server, or in between.
 
-If you get this error, one thing you could try would be to fiddle
-with the setting of \q{Miscomputes SSH-2 encryption keys} on the Bugs
-panel (see \k{config-ssh-bug-derivekey2}).
+If you get this error, one thing you could try would be to fiddle with
+the setting of \q{Miscomputes SSH-2 encryption keys} (see
+\k{config-ssh-bug-derivekey2}) or \q{Ignores SSH-2 maximum packet
+size} (see \k{config-ssh-bug-maxpkt2}) on the Bugs panel .
 
 Another known server problem which can cause this error is described
 in \k{faq-openssh-bad-openssl} in the FAQ.