-\versionid $Id: faq.but,v 1.76 2004/08/20 08:32:30 jacob Exp $
+\define{versionidfaq} \versionid $Id$
\A{faq} PuTTY FAQ
If you have host keys available in the common \c{known_hosts} format,
we have a script called
-\W{http://cvs.tartarus.org/putty/contrib/kh2reg.py}\c{kh2reg.py}
+\W{http://www.tartarus.org/~simon-anonsvn/viewcvs.cgi/putty/contrib/kh2reg.py?view=markup}\c{kh2reg.py}
to convert them to a Windows .REG file, which can be installed ahead of
time by double-clicking or using \c{REGEDIT}.
Terminal Services have found that doing so no longer works since
they upgraded to WinXP SP2.
-This is an issue with SP2 that is acknowledged by Microsoft in
-MS Knowledge Base article
+This is apparently an issue with SP2 that is acknowledged by Microsoft
+in MS Knowledge Base article
\W{http://support.microsoft.com/default.aspx?scid=kb;en-us;884020}{884020}.
-
-For a fix, you'll need to contact Microsoft support. We've been told
-that the process is reasonably easy, and is free of charge; and that
-the fix will be included in the next Windows XP Service Pack (but
-probably not before).
+The article links to a fix you can download.
(\e{However}, we've been told that SP2 \e{also} fixes the bug that
means you need to use non-\cw{127.0.0.1} addresses to forward
-Terminal Services.)
+Terminal Services in the first place.)
+
+\S{faq-missing-slash}{Question} PSFTP commands seem to be missing a
+directory separator (slash).
+
+Some people have reported the following incorrect behaviour with
+PSFTP:
+
+\c psftp> pwd
+\e iii
+\c Remote directory is /dir1/dir2
+\c psftp> get filename.ext
+\e iiiiiiiiiiiiiiii
+\c /dir1/dir2filename.ext: no such file or directory
+
+This is not a bug in PSFTP. There is a known bug in some versions of
+portable OpenSSH
+(\W{http://bugzilla.mindrot.org/show_bug.cgi?id=697}{bug 697}) that
+causes these symptoms; it appears to have been introduced around
+3.7.x. It manifests only on certain platforms (AIX is what has been
+reported to us).
+
+There is a patch for OpenSSH attached to that bug; it's also fixed in
+recent versions of portable OpenSSH (from around 3.8).
\H{faq-secure} Security questions
Also, security reasons. PuTTY is a security product, and as such it
is particularly important to guard the code and the web site against
unauthorised modifications which might introduce subtle security
-flaws. Therefore, we prefer that the CVS repository, web site and
+flaws. Therefore, we prefer that the Subversion repository, web site and
FTP site remain where they are, under the direct control of system
administrators we know and trust personally, rather than being run
by a large organisation full of people we've never met and which is
If someone else wants to set up a mailing list or other forum for
PuTTY users to help each other with common problems, that would be
fine with us, though the PuTTY team would almost certainly not have the
-time to read it. It's probably better to use the established
-newsgroup \cw{comp.security.ssh} for this purpose.
+time to read it. It's probably better to use one of the established
+newsgroups for this purpose (see \k{feedback-other-fora}).
\S{faq-donations}{Question} How can I donate to PuTTY development?
Yes. You need not bother asking us explicitly for permission. You
already have permission. Redistribution of the unmodified PuTTY
-binary in this way is entirely permitted by our licence, and you are
-welcome to do it as much as you like.
+binary in this way is entirely permitted by our licence (see
+\k{licence}), and you are welcome to do it as much as you like.
If you are distributing PuTTY within your own organisation, or for
use with your own product, then we recommend (but do not insist)
projects / u / mdw / putty / blobdiff