X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=doc%2Ferrors.but;h=2c4385e6c03fafdda2aa7cec8ba6426db1712407;hb=3fc33c4118acebbd6bb37f69b71a707aaa2f7ce8;hp=64409eae208e4fbcaa456b9fe5b4b48b0999a694;hpb=63c26e722a84497734bf212dcb8a66212142797d;p=PuTTY.git diff --git a/doc/errors.but b/doc/errors.but index 64409eae..2c4385e6 100644 --- a/doc/errors.but +++ b/doc/errors.but @@ -15,6 +15,8 @@ bug (see \k{feedback}) and we will add documentation for it. \H{errors-hostkey-absent} \q{The server's host key is not cached in the registry} +\cfg{winhelp-topic}{errors.hostkey.absent} + This error message occurs when PuTTY connects to a new SSH server. Every server identifies itself by means of a host key; once PuTTY knows the host key for a server, it will be able to detect if a @@ -36,6 +38,8 @@ See \k{gs-hostkey} for more information on host keys. \H{errors-hostkey-wrong} \q{WARNING - POTENTIAL SECURITY BREACH!} +\cfg{winhelp-topic}{errors.hostkey.changed} + This message, followed by \q{The server's host key does not match the one PuTTY has cached in the registry}, means that PuTTY has connected to the SSH server before, knows what its host key @@ -69,7 +73,8 @@ this, let us know and we'll move it up our priority list. ... 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. @@ -125,9 +130,11 @@ Similarly, any error message starting with \q{Assertion failed} is a bug in PuTTY. Please report it to us, and include the exact text from the error message box. -\H{errors-key-wrong-format} \q{Unable to use this private key file}, +\H{errors-cant-load-key} \q{Unable to use this private key file}, \q{Couldn't load private key}, \q{Key is of wrong type} +\cfg{winhelp-topic}{errors.cantloadkey} + Various forms of this error are printed in the PuTTY window, or written to the PuTTY Event Log (see \k{using-eventlog}) when trying public-key authentication, or given by Pageant when trying to load a @@ -272,6 +279,10 @@ connection out. See \k{faq-idleout} in the FAQ for more details. You 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