X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/9bb8630af3373e7bbf594bfeda731585684e1b69..4494be0aa8c4b88c1c9c46318fcbf23e9f47f3d6:/doc/errors.but

diff --git a/doc/errors.but b/doc/errors.but
index 59338ebc..66579ef6 100644
--- a/doc/errors.but
+++ b/doc/errors.but
@@ -1,4 +1,4 @@
-\versionid $Id: errors.but,v 1.8 2004/05/20 12:48:19 simon Exp $
+\versionid $Id: errors.but,v 1.10 2004/09/27 00:23:19 jacob Exp $
 
 \C{errors} Common error messages
 
@@ -125,6 +125,28 @@ 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},
+\q{Couldn't load private key}, \q{Key is of wrong type}
+
+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
+private key.
+
+If you see one of these messages, it often indicates that you've tried
+to load a key of an inappropriate type into PuTTY, Plink, PSCP, PSFTP,
+or Pageant.
+
+You may have specified a key that's inappropriate for the connection
+you're making. The SSH-1 and SSH-2 protocols require different private
+key formats, and a SSH-1 key can't be used for a SSH-2 connection (or
+vice versa).
+
+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,
+in which case you need to import it into PuTTY's native format
+(\c{*.PPK}) using PuTTYgen - see \k{puttygen-conversions}.
+
 \H{errors-refused} \q{Server refused our public key} or \q{Key
 refused}
 
@@ -178,8 +200,8 @@ A known server problem which can cause this error is described in
 This error occurs when PuTTY decrypts an SSH packet and the
 decrypted data makes no sense. This probably means something has
 gone wrong in the encryption or decryption process. It's difficult
-to tell from this error message whether the problem is in the client
-or in the server.
+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 SSH2 encryption keys} on the Bugs