SHA-256 implementation, for use in future KEX algorithms, in particular

[sgt/putty] / doc / config.but

diff --git a/doc/config.but b/doc/config.but
index d077c4a..2647189 100644 (file)
--- a/doc/config.but
+++ b/doc/config.but
@@ -2052,6 +2052,9 @@ Instead, you can choose to run a single specific command (such as a
 mail user agent, for example). If you want to do this, enter the
 command in the \q{\ii{Remote command}} box.
 
 mail user agent, for example). If you want to do this, enter the
 command in the \q{\ii{Remote command}} box.
 

+Note that most servers will close the session after executing the
+command.
+

 \S{config-ssh-noshell} \q{Don't start a \I{remote shell}shell or
 \I{remote command}command at all}
 
 \S{config-ssh-noshell} \q{Don't start a \I{remote shell}shell or
 \I{remote command}command at all}
 


@@ -2116,9 +2119,9 @@ PuTTY currently supports the following algorithms:
 
 \b \i{Arcfour} (RC4) - 256 or 128-bit stream cipher (SSH-2 only)
 
 
 \b \i{Arcfour} (RC4) - 256 or 128-bit stream cipher (SSH-2 only)
 

-\b \i{Blowfish} - 128-bit CBC
+\b \i{Blowfish} - 256-bit SDCTR (SSH-2 only) or 128-bit CBC

 
 

-\b \ii{Triple-DES} - 168-bit CBC
+\b \ii{Triple-DES} - 168-bit SDCTR (SSH-2 only) or CBC

 
 \b \ii{Single-DES} - 56-bit CBC (see below for SSH-2)
 
 
 \b \ii{Single-DES} - 56-bit CBC (see below for SSH-2)
 


@@ -2278,16 +2281,33 @@ protection than SSH-2 without rekeys.
 The Auth panel allows you to configure \i{authentication} options for
 SSH sessions.
 
 The Auth panel allows you to configure \i{authentication} options for
 SSH sessions.
 

+\S{config-ssh-noauth} \q{Bypass authentication entirely}
+
+\cfg{winhelp-topic}{ssh.auth.bypass}
+
+In SSH-2, it is possible to establish a connection without using SSH's
+mechanisms to identify or authenticate oneself to the server. Some
+servers may prefer to handle authentication in the data channel, for
+instance, or may simply require no authentication whatsoever.
+
+By default, PuTTY assumes the server requires authentication (most
+do), and thus must provide a username. If you find you are getting
+unwanted username prompts, you could try checking this option.
+
+This option only affects SSH-2 connections. SSH-1 connections always
+require an authentication step.
+

 \S{config-ssh-tis} \q{Attempt \I{TIS authentication}TIS or
 \i{CryptoCard authentication}}
 
 \cfg{winhelp-topic}{ssh.auth.tis}
 
 \S{config-ssh-tis} \q{Attempt \I{TIS authentication}TIS or
 \i{CryptoCard authentication}}
 
 \cfg{winhelp-topic}{ssh.auth.tis}
 

-TIS and CryptoCard authentication are simple \I{challenge/response
-authentication}challenge/response forms of authentication available in
-SSH protocol version 1 only. You might use them if you were using \i{S/Key}
-\i{one-time passwords}, for example, or if you had a physical \i{security
-token} that generated responses to authentication challenges.
+TIS and CryptoCard authentication are (despite their names) generic
+forms of simple \I{challenge/response authentication}challenge/response
+authentication available in SSH protocol version 1 only. You might use
+them if you were using \i{S/Key} \i{one-time passwords}, for example,
+or if you had a physical \i{security token} that generated responses
+to authentication challenges.

 
 With this switch enabled, PuTTY will attempt these forms of
 authentication if the server is willing to try them. You will be
 
 With this switch enabled, PuTTY will attempt these forms of
 authentication if the server is willing to try them. You will be