Update documentation for 0.68.

[PuTTY.git] / doc / faq.but

diff --git a/doc/faq.but b/doc/faq.but
index 03de70d780ebfd657c4cfb87145a7858f0e00f1b..9c7b9a65e5372050371b9d04dd6be9c98b9bd648 100644 (file)
--- a/doc/faq.but
+++ b/doc/faq.but
@@ -66,9 +66,8 @@ Yes. SSH-1 support has always been available in PuTTY.
 However, the SSH-1 protocol has many weaknesses and is no longer
 considered secure; you should use SSH-2 instead if at all possible.
 
-\#{XXX-REVIEW-BEFORE-RELEASE:
 As of 0.68, PuTTY will no longer fall back to SSH-1 if the server
-doesn't appear to support SSH-2; you must explicitly ask for SSH-1. }
+doesn't appear to support SSH-2; you must explicitly ask for SSH-1.
 
 \S{faq-localecho}{Question} Does PuTTY support \i{local echo}?
 
@@ -257,10 +256,9 @@ If you look at the source release, you should find a \c{unix}
 subdirectory. There are a couple of ways of building it,
 including the usual \c{configure}/\c{make}; see the file \c{README}
 in the source distribution. This should build you Unix
-ports of Plink, PuTTY itself, PuTTYgen, PSCP, PSFTP, and also
+ports of Plink, PuTTY itself, PuTTYgen, PSCP, PSFTP, Pageant, and also
 \i\c{pterm} - an \cw{xterm}-type program which supports the same
-terminal emulation as PuTTY. \#{XXX-REVIEW-BEFORE-RELEASE:}
-We do not yet have a Unix port of Pageant.
+terminal emulation as PuTTY.
 
 If you don't have \i{Gtk}, you should still be able to build the
 command-line tools.