Buttress is now Halibut: change the docs makefile.

[sgt/putty] / doc / faq.but

diff --git a/doc/faq.but b/doc/faq.but
index 1d849a3..e2577bf 100644 (file)
--- a/doc/faq.but
+++ b/doc/faq.but
@@ -1,4 +1,4 @@
-\versionid $Id: faq.but,v 1.24 2002/04/01 15:18:29 simon Exp $
+\versionid $Id: faq.but,v 1.30 2002/07/09 11:34:10 jacob Exp $
 
 \A{faq} PuTTY FAQ
 
@@ -37,10 +37,9 @@ version 0.52.
 \S{faq-ssh2-keyfmt}{Question} Does PuTTY support reading OpenSSH or
 \cw{ssh.com} SSHv2 private key files?
 
-Not at present. OpenSSH and \cw{ssh.com} have totally different
-formats for private key files, and neither one is particularly
-pleasant, so PuTTY has its own. We do plan to write a converter at
-some stage.
+Version 0.52 doesn't, but in the latest development snapshots
+PuTTYgen can load and save both OpenSSH and \cw{ssh.com} private key
+files.
 
 \S{faq-ssh1}{Question} Does PuTTY support SSH v1?
 
@@ -739,6 +738,21 @@ For more details and OpenSSH patches, see
 \W{http://bugzilla.mindrot.org/show_bug.cgi?id=138}{bug 138} in the
 OpenSSH BTS.
 
+\e{Update:} As of OpenSSH 3.4p1 the problem with SSH 1 and Blowfish
+remains. Apply the patch linked to from bug 138, or use another cipher
+(e.g., 3DES) instead.
+
+\S{faq-ssh2key-ssh1conn}{Question} Why do I see "Couldn't load private
+key from ..."? Why can PuTTYgen load my key but not PuTTY?
+
+It's likely that you've generated an SSH protocol 2 key with PuTTYgen,
+but you're trying to use it in an SSH 1 connection. SSH1 and SSH2 keys
+have different formats, and (at least in 0.52) PuTTY's reporting of a
+key in the wrong format isn't optimal.
+
+To connect using SSH 2 to a server that supports both versions, you
+need to change the configuration from the default (see \k{faq-ssh2}).
+
 \H{faq-secure} Security questions
 
 \S{faq-publicpc}{Question} Is it safe for me to download PuTTY and