From 960e03a5bd2efd92ad15d5d39577e698e35f034f Mon Sep 17 00:00:00 2001 From: jacob Date: Wed, 1 Sep 2004 10:12:41 +0000 Subject: [PATCH] Documentation existence of SOCKS5 CHAP authentication. git-svn-id: svn://svn.tartarus.org/sgt/putty@4522 cda61777-01e9-0310-a592-d414129be87e --- doc/config.but | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/doc/config.but b/doc/config.but index 86102030..21b67ba3 100644 --- a/doc/config.but +++ b/doc/config.but @@ -1,4 +1,4 @@ -\versionid $Id: config.but,v 1.86 2004/07/22 11:18:08 jacob Exp $ +\versionid $Id: config.but,v 1.87 2004/09/01 10:12:41 jacob Exp $ \C{config} Configuring PuTTY @@ -1675,6 +1675,18 @@ Authentication is not fully supported for all forms of proxy: \b Username and password authentication is supported for HTTP proxies and SOCKS 5 proxies. +\lcont{ + +\b With SOCKS 5, authentication is via \i{CHAP} if the proxy +supports it (this is not supported in \i{PuTTYtel}); otherwise the +password is sent to the proxy in plain text. + +\b With HTTP proxying, the only currently supported authentication +method is \q{basic}, where the password is sent to proxy in plain +text. + +} + \b SOCKS 4 can use the \q{Username} field, but does not support passwords. -- 2.11.0