Try to make it slightly clearer that TIS/CryptoCard are generic, since

SSH:TDGv2 seems to think that TIS is only relevant to its original
application (whose name eludes me at the moment).

git-svn-id: svn://svn.tartarus.org/sgt/putty@6038 cda61777-01e9-0310-a592-d414129be87e

diff --git a/doc/config.but b/doc/config.but
index aae0b39..e48c588 100644 (file)
--- a/doc/config.but
+++ b/doc/config.but
@@ -2299,11 +2299,12 @@ require an authentication step.
 
 \cfg{winhelp-topic}{ssh.auth.tis}
 
 
 \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