nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-25 09:12:24 +00:00
Code Issues Projects Releases Wiki Activity

Docs: tweak other error messages for truth.

Browse Source
This commit is contained in:
Jacob Nevins 2019-04-19 15:42:14 +01:00
parent c86a56f49c
commit 461844a5ec
1 changed files with 11 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/errors.but
View File

@ -76,10 +76,14 @@ attack.
This occurs when the SSH server does not offer any ciphers which you This occurs when the SSH server does not offer any ciphers which you
have configured PuTTY to consider strong enough. By default, PuTTY have configured PuTTY to consider strong enough. By default, PuTTY
puts up this warning only for \ii{single-DES} and \i{Arcfour} encryption. puts up this warning only for \i{Blowfish}, \ii{single-DES}, and
\i{Arcfour} encryption.
See \k{config-ssh-encryption} for more information on this message. See \k{config-ssh-encryption} for more information on this message.
(There are similar messages for other cryptographic primitives, such
as host key algorithms.)
\H{errors-toomanyauth} \q{Remote side sent disconnect message type 2 \H{errors-toomanyauth} \q{Remote side sent disconnect message type 2
(protocol error): "Too many authentication failures for root"} (protocol error): "Too many authentication failures for root"}
@ -137,8 +141,8 @@ Similarly, any error message starting with \q{Assertion failed} is a
bug in PuTTY. Please report it to us, and include the exact text bug in PuTTY. Please report it to us, and include the exact text
from the error message box. from the error message box.
\H{errors-cant-load-key} \q{Unable to use this private key file}, \H{errors-cant-load-key} \q{Unable to use key file},
\q{Couldn't load private key}, \q{Key is of wrong type} \q{Couldn't load private key}, \q{Couldn't load this key}
Various forms of this error are printed in the PuTTY window, or Various forms of this error are printed in the PuTTY window, or
written to the PuTTY Event Log (see \k{using-eventlog}) when trying written to the PuTTY Event Log (see \k{using-eventlog}) when trying
@ -157,10 +161,10 @@ vice versa).
Alternatively, you may have tried to load an SSH-2 key in a \q{foreign} Alternatively, you may have tried to load an SSH-2 key in a \q{foreign}
format (OpenSSH or \cw{ssh.com}) directly into one of the PuTTY tools, format (OpenSSH or \cw{ssh.com}) directly into one of the PuTTY tools,
in which case you need to import it into PuTTY's native format in which case you need to import it into PuTTY's native format
(\c{*.PPK}) using PuTTYgen - see \k{puttygen-conversions}. (\c{*.PPK}) using PuTTYgen \dash see \k{puttygen-conversions}.
\H{errors-refused} \q{Server refused our public key} or \q{Key \H{errors-refused} \q{Server refused our key},
refused} \q{Server refused our public key}, \q{Key refused}
Various forms of this error are printed in the PuTTY window, or Various forms of this error are printed in the PuTTY window, or
written to the PuTTY Event Log (see \k{using-eventlog}) when trying written to the PuTTY Event Log (see \k{using-eventlog}) when trying
@ -205,7 +209,7 @@ Upgrade your server, or use the workarounds described in
This error indicates that PuTTY has run out of ways to authenticate This error indicates that PuTTY has run out of ways to authenticate
you to an SSH server. This may be because PuTTY has TIS or you to an SSH server. This may be because PuTTY has TIS or
keyboard-interactive authentication disabled, in which case keyboard-interactive authentication disabled, in which case see
\k{config-ssh-tis} and \k{config-ssh-ki}. \k{config-ssh-tis} and \k{config-ssh-ki}.
\H{errors-crc} \q{Incorrect \i{CRC} received on packet} or \q{Incorrect \H{errors-crc} \q{Incorrect \i{CRC} received on packet} or \q{Incorrect