Fix punctuation in public key docs.

[PuTTY.git] / doc / errors.but

diff --git a/doc/errors.but b/doc/errors.but
index 5a0d83dc966d31ab24c1cf5dfc4d914316506c7d..bf9672d05a0c7d28a268aef0565dc1cba08c6e55 100644 (file)
--- a/doc/errors.but
+++ b/doc/errors.but
@@ -1,5 +1,3 @@
-\define{versioniderrors} \versionid $Id$
-

 \C{errors} Common \i{error messages}
 
 This chapter lists a number of common error messages which PuTTY and
 \C{errors} Common \i{error messages}
 
 This chapter lists a number of common error messages which PuTTY and


@@ -58,17 +56,6 @@ in the same way as you would if it was new.
 
 See \k{gs-hostkey} for more information on host keys.
 
 
 See \k{gs-hostkey} for more information on host keys.
 

-\H{errors-portfwd-space} \q{Out of space for port forwardings}
-
-PuTTY has a fixed-size buffer which it uses to store the details of
-all \i{port forwardings} you have set up in an SSH session. If you
-specify too many port forwardings on the PuTTY or Plink command line
-and this buffer becomes full, you will see this error message.
-
-We need to fix this (fixed-size buffers are almost always a mistake)
-but we haven't got round to it. If you actually have trouble with
-this, let us know and we'll move it up our priority list.
-

 \H{errors-cipher-warning} \q{The first cipher supported by the server is
 ... below the configured warning threshold}
 
 \H{errors-cipher-warning} \q{The first cipher supported by the server is
 ... below the configured warning threshold}
 


@@ -182,6 +169,9 @@ user's home directory on the server. Also, read the PuTTY Event Log;
 the server may have sent diagnostic messages explaining exactly what
 problem it had with your setup.
 
 the server may have sent diagnostic messages explaining exactly what
 problem it had with your setup.
 

+\K{pubkey-gettingready} has some hints on server-side public key
+setup.
+

 \H{errors-access-denied} \q{Access denied}, \q{Authentication refused}
 
 Various forms of this error are printed in the PuTTY window, or
 \H{errors-access-denied} \q{Access denied}, \q{Authentication refused}
 
 Various forms of this error are printed in the PuTTY window, or


@@ -235,9 +225,10 @@ gone wrong in the encryption or decryption process. It's difficult
 to tell from this error message whether the problem is in the client,
 in the server, or in between.
 
 to tell from this error message whether the problem is in the client,
 in the server, or in between.
 

-If you get this error, one thing you could try would be to fiddle
-with the setting of \q{Miscomputes SSH-2 encryption keys} on the Bugs
-panel (see \k{config-ssh-bug-derivekey2}).
+If you get this error, one thing you could try would be to fiddle with
+the setting of \q{Miscomputes SSH-2 encryption keys} (see
+\k{config-ssh-bug-derivekey2}) or \q{Ignores SSH-2 maximum packet
+size} (see \k{config-ssh-bug-maxpkt2}) on the Bugs panel .

 
 Another known server problem which can cause this error is described
 in \k{faq-openssh-bad-openssl} in the FAQ.
 
 Another known server problem which can cause this error is described
 in \k{faq-openssh-bad-openssl} in the FAQ.


@@ -347,3 +338,13 @@ things into PuTTY while the network is down, but it can also occur
 if PuTTY decides of its own accord to send data: due to a repeat key
 exchange in SSH-2 (see \k{config-ssh-kex-rekey}) or due to
 keepalives (\k{config-keepalive}).
 if PuTTY decides of its own accord to send data: due to a repeat key
 exchange in SSH-2 (see \k{config-ssh-kex-rekey}) or due to
 keepalives (\k{config-keepalive}).

+
+\H{errors-cannotassignaddress} \q{Network error: Cannot assign requested
+address}
+
+This means that the operating system rejected the parameters of the
+network connection PuTTY tried to make, usually without actually
+trying to connect to anything, because they were simply invalid.
+
+A common way to provoke this error is to accidentally try to connect
+to port 0, which is not a valid port number.