Turns out that the compose-keys fix in r9567 did in fact break one

[PuTTY.git] / doc / errors.but

diff --git a/doc/errors.but b/doc/errors.but
index ae00a410b916c909f2a93225a3de505ae46e3f4d..06c247c01e4c465ac35c2f4659b0af9aa5fa5546 100644 (file)
--- 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