Beef up the `unfinished and experimental' warnings for the two Mac

[u/mdw/putty] / doc / faq.but

diff --git a/doc/faq.but b/doc/faq.but
index 5ac7b34..a6a99a2 100644 (file)
--- a/doc/faq.but
+++ b/doc/faq.but
@@ -84,6 +84,7 @@ options}.
 so I don't have to change them every time?
 
 Yes, all of PuTTY's settings can be saved in named session profiles.
 so I don't have to change them every time?
 
 Yes, all of PuTTY's settings can be saved in named session profiles.

+You can also change the default settings that are used for new sessions.

 See \k{config-saving} in the documentation for how to do this.
 
 \S{faq-disksettings}{Question} Does PuTTY support storing its
 See \k{config-saving} in the documentation for how to do this.
 
 \S{faq-disksettings}{Question} Does PuTTY support storing its


@@ -380,12 +381,12 @@ while host keys are stored under \c{SshHostKeys}.
 
 PuTTY also requires a random number seed file, to improve the
 unpredictability of randomly chosen data needed as part of the SSH
 
 PuTTY also requires a random number seed file, to improve the
 unpredictability of randomly chosen data needed as part of the SSH

-cryptography. This is stored by default in your Windows home
-directory (\c{%HOMEDRIVE%\\%HOMEPATH%}), or in the actual Windows
-directory (such as \c{C:\\WINDOWS}) if the home directory doesn't
-exist, for example if you're using Win95. If you want to change the
-location of the random number seed file, you can put your chosen
-pathname in the Registry, at
+cryptography. This is stored by default in a file called \i\c{PUTTY.RND}
+in your Windows home directory (\c{%HOMEDRIVE%\\%HOMEPATH%}), or in
+the actual Windows directory (such as \c{C:\\WINDOWS}) if the home
+directory doesn't exist, for example if you're using Win95. If you
+want to change the location of the random number seed file, you can
+put your chosen pathname in the Registry, at

 
 \c HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\RandSeedFile
 
 
 \c HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\RandSeedFile
 


@@ -729,14 +730,16 @@ change is
 \W{http://support.microsoft.com/default.aspx?scid=kb;en-us;158474}{158474}
 for more information.)
 
 \W{http://support.microsoft.com/default.aspx?scid=kb;en-us;158474}{158474}
 for more information.)
 

-On Windows NT or 2000, the registry key is
+On Windows NT, 2000, or XP, the registry key to create or change is

 
 \c HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\
 \c   Parameters\TcpMaxDataRetransmissions
 
 and it must be of type DWORD.
 
 \c HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\
 \c   Parameters\TcpMaxDataRetransmissions
 
 and it must be of type DWORD.

-(See MS Knowledge Base article
+(See MS Knowledge Base articles

 \W{http://support.microsoft.com/default.aspx?scid=kb;en-us;120642}{120642}
 \W{http://support.microsoft.com/default.aspx?scid=kb;en-us;120642}{120642}

+and
+\W{http://support.microsoft.com/default.aspx?scid=kb;en-us;314053}{314053}

 for more information.)
 
 Set the key's value to something like 10. This will cause Windows to
 for more information.)
 
 Set the key's value to something like 10. This will cause Windows to


@@ -838,13 +841,13 @@ default cipher differs from many other clients.)
 
 \e{OpenSSH 3.1p1:} configurations known to be broken (and symptoms):
 
 
 \e{OpenSSH 3.1p1:} configurations known to be broken (and symptoms):
 

-\b SSH-2 with AES cipher (PuTTY says "Assertion failed! Expression:
-(len & 15) == 0" in sshaes.c, or "Out of memory", or crashes)
+\b SSH-2 with AES cipher (PuTTY says \q{Assertion failed! Expression:
+(len & 15) == 0} in \cw{sshaes.c}, or \q{Out of memory}, or crashes)

 
 

-\b SSH-2 with 3DES (PuTTY says "Incorrect MAC received on packet")
+\b SSH-2 with 3DES (PuTTY says \q{Incorrect MAC received on packet})

 
 

-\b SSH-1 with Blowfish (PuTTY says "Incorrect CRC received on
-packet")
+\b SSH-1 with Blowfish (PuTTY says \q{Incorrect CRC received on
+packet})

 
 \b SSH-1 with 3DES
 
 
 \b SSH-1 with 3DES
 


@@ -856,8 +859,8 @@ bug 138 above, or use another cipher (e.g., 3DES) instead.
 and workarounds with older versions of OpenSSH, although it's not
 clear the underlying cause is the same.
 
 and workarounds with older versions of OpenSSH, although it's not
 clear the underlying cause is the same.
 

-\S{faq-ssh2key-ssh1conn}{Question} Why do I see "Couldn't load private
-key from ..."? Why can PuTTYgen load my key but not PuTTY?
+\S{faq-ssh2key-ssh1conn}{Question} Why do I see \q{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. SSH-1 and SSH-2 keys
 
 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. SSH-1 and SSH-2 keys