~mdw
/
sgt
/
putty
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Support username/password authentication in SOCKS 5.
[sgt/putty]
/
doc
/
config.but
diff --git
a/doc/config.but
b/doc/config.but
index
c2383b6
..
50f16e7
100644
(file)
--- a/
doc/config.but
+++ b/
doc/config.but
@@
-1,4
+1,4
@@
-\versionid $Id: config.but,v 1.
39 2002/09/21 14:03:05
simon Exp $
+\versionid $Id: config.but,v 1.
40 2002/09/21 16:07:43
simon Exp $
\C{config} Configuring PuTTY
\C{config} Configuring PuTTY
@@
-1433,15
+1433,14
@@
This excludes both of the above ranges at once.
If your proxy requires authentication, you can enter a username and
a password in the \q{Username} and \q{Password} boxes.
If your proxy requires authentication, you can enter a username and
a password in the \q{Username} and \q{Password} boxes.
-Authentication is not supported for all forms of proxy
. Currently
:
+Authentication is not supported for all forms of proxy:
-\b Username and password authentication is supported for HTTP proxies.
+\b Username and password authentication is supported for HTTP
+proxies and SOCKS 5 proxies.
\b SOCKS 4 can use the \q{Username} field, but does not support
passwords.
\b SOCKS 4 can use the \q{Username} field, but does not support
passwords.
-\b PuTTY does not support authentication in SOCKS 5 at all.
-
\b Authentication is meaningless in Telnet proxies.
\S{config-proxy-command} Specifying the Telnet proxy command
\b Authentication is meaningless in Telnet proxies.
\S{config-proxy-command} Specifying the Telnet proxy command