... below the configured warning threshold}
This occurs when the SSH server does not offer any ciphers which you
-have configured PuTTY to consider strong enough.
+have configured PuTTY to consider strong enough. By default, PuTTY
+puts up this warning only for single-DES encryption.
See \k{config-ssh-encryption} for more information on this message.
This is almost certainly not a problem with PuTTY. If you see this
type of message, the first thing you should do is check your
-\e{server} configuration carefully. Also, read the PuTTY Event Log;
+\e{server} configuration carefully. Common errors include having
+the wrong permissions or ownership set on the public key or the
+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.
abort}
This is a generic error produced by the Windows network code when it
-decides that your network connection is dead. For example, it might
+kills an established connection for some reason. For example, it might
happen if you pull the network cable out of the back of an
Ethernet-connected computer, or if Windows has any other similar
reason to believe the entire network has become unreachable.
may be able to improve the situation by using keepalives; see
\k{config-keepalive} for details on this.
+Note that Windows can produce this error in some circumstances without
+seeing a connection reset from the server, for instance if the
+connection to the network is lost.
+
\H{errors-connrefused} \q{Network error: Connection refused}
This error means that the network connection PuTTY tried to make to