Makefile fix: we've been compiling ssh.c separately because it needs

[sgt/putty] / doc / faq.but

diff --git a/doc/faq.but b/doc/faq.but
index 7836eb6..dd48c8b 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.
 
 \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
 \H{faq-ports} Ports to other operating systems
 
 The eventual goal is for PuTTY to be a multi-platform program, able


@@ -272,6 +287,21 @@ Windows users don't have a middle button at all.
 
 You can also paste by pressing Shift-Ins.
 
 
 You can also paste by pressing Shift-Ins.
 

+\S{faq-tunnels} How do I use X forwarding and port forwarding? I
+can't find the Tunnels panel.
+
+If you're looking in the 0.51 release or earlier, the Tunnels panel
+isn't there. It was added in the development snapshots after 0.51,
+and releases 0.52 and onwards will contain it.
+
+\S{faq-options} How do I use all PuTTY's features (port forwarding,
+SSH v2 etc) in Plink?
+
+Plink is currently rather short of command line options to enable
+this sort of thing. You can use these features if you create a PuTTY
+saved session, and then use the name of the saved session on Plink's
+command line in place of a hostname.
+

 \S{faq-pscp} How do I use PSCP.EXE? When I double-click it gives me
 a command prompt window which then closes instantly.
 
 \S{faq-pscp} How do I use PSCP.EXE? When I double-click it gives me
 a command prompt window which then closes instantly.
 


@@ -306,8 +336,6 @@ command will give an error message:
 \c c:\>pscp user@host:"\"oo er\"" .
 \c warning: remote host tried to write to a file called 'oo er'
 \c          when we requested a file called '"oo er"'.
 \c c:\>pscp user@host:"\"oo er\"" .
 \c warning: remote host tried to write to a file called 'oo er'
 \c          when we requested a file called '"oo er"'.

-\c          If this is a wildcard, consider upgrading to SSH 2 or using
-\c          the '-unsafe' option. Renaming of this file has been disallowed.

 
 Instead, you need to specify the local file name in full:
 
 
 Instead, you need to specify the local file name in full:
 


@@ -342,6 +370,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.
 
 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.
 
 \S{faq-colours} I clicked on a colour in the Colours panel, and the
 colour didn't change in my terminal.
 


@@ -485,6 +517,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.
 
 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
 \H{faq-secure} Security questions
 
 \S{faq-publicpc} Is it safe for me to download PuTTY and use it on a