Add the `will you write an SSH server' question to the FAQ.

[sgt/putty] / doc / faq.but

diff --git a/doc/faq.but b/doc/faq.but
index 9c2cff4..f43a558 100644 (file)
--- a/doc/faq.but
+++ b/doc/faq.but
@@ -101,6 +101,21 @@ authentication, which is more flexible and more secure. See
 \k{pubkey} in the documentation for a full discussion of public key
 authentication.
 
+\S{faq-server} Will you write an SSH server for the PuTTY suite, to
+go with the client?
+
+No. The only reason we might want to would be if we could easily
+re-use existing code and significantly cut down the effort. We don't
+believe this is the case; there just isn't enough common ground
+between an SSH client and server to make it worthwhile.
+
+If someone else wants to use bits of PuTTY in the process of writing
+a Windows SSH server, they'd be perfectly welcome to of course, but
+I really can't see it being a lot less effort for us to do that than
+it would be for us to write a server from the ground up. We don't
+have time, and we don't have motivation. The code is available if
+anyone else wants to try it.
+
 \H{faq-ports} Ports to other operating systems
 
 The eventual goal is for PuTTY to be a multi-platform program, able
@@ -304,10 +319,12 @@ match (unless you specified the \c{-unsafe} option). The following
 command will give an error message:
 
 \c c:\>pscp user@host:"\"oo er\"" .
-\c warning: remote host tried to write to a file called 'a b'
-\c          when we requested a file called '"a b"'.
-\c          If this is a wildcard, consider upgrading to SSH 2 or using
-\c          the '-unsafe' option. Renaming of this file has been disallowed.
+\c warning: remote host tried to write to a file called 'oo er'
+\c          when we requested a file called '"oo er"'.
+
+Instead, you need to specify the local file name in full:
+
+\c c:\>pscp user@host:"\"oo er\"" "oo er"
 
 If PSCP is using the newer SFTP protocol, none of this is a problem,
 and all filenames with spaces in are specified using a single pair
@@ -338,6 +355,10 @@ workaround without the user needing to ask. Therefore you \e{should}
 never have to use this option again after 0.52, but it is still
 provided just in case another buggy server shows up.
 
+In this context MAC stands for Message Authentication Code. It's a
+cryptographic term, and it has nothing at all to do with Ethernet
+MAC (Media Access Control) addresses.
+
 \S{faq-colours} I clicked on a colour in the Colours panel, and the
 colour didn't change in my terminal.
 
@@ -381,8 +402,8 @@ get this wrong.
 The bug has been fixed since version 0.51, so upgrading to a later
 version or snapshot should solve the problem.
 
-\S{faq-outofmem} After trying to establish an SSH connection, PuTTY
-says \q{Out of memory} and dies.
+\S{faq-outofmem} After trying to establish an SSH 2 connection,
+PuTTY says \q{Out of memory} and dies.
 
 If this happens just while the connection is starting up, this often
 indicates that for some reason the client and server have failed to
@@ -481,6 +502,17 @@ your terminal runs the risk of sending the same control sequence by
 accident, and cause unexpected changes in the window title. Don't do
 it.
 
+\S{faq-password} My keyboard stops working once PuTTY displays the
+password prompt.
+
+No, it doesn't. PuTTY just doesn't display the password you type, so
+that someone looking at your screen can't see what it is.
+
+Unlike the Windows login prompts, PuTTY doesn't display the password
+as a row of asterisks either. This is so that someone looking at
+your screen can't even tell how \e{long} your password is, which
+might be valuable information.
+
 \H{faq-secure} Security questions
 
 \S{faq-publicpc} Is it safe for me to download PuTTY and use it on a