summaryrefslogtreecommitdiff
path: root/FAQ
diff options
context:
space:
mode:
authorFrank Cusack <fcusack@fcusack.com>2002-10-27 13:19:37 +0000
committerFrank Cusack <fcusack@fcusack.com>2002-10-27 13:19:37 +0000
commit767b224b09e000895b0918937edd19041e40e6f6 (patch)
tree20685473ffb3851b018e95367bbafda957a1ea11 /FAQ
parentaefcf5ac90dee434d605167b6a719c58c0ffcf03 (diff)
downloadppp-767b224b09e000895b0918937edd19041e40e6f6.tar.gz
Update for mschapv2 and clarify client/server (authenticatee/authenticator).
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ6
1 files changed, 4 insertions, 2 deletions
diff --git a/FAQ b/FAQ
index 96bc5c7..035da4b 100644
--- a/FAQ
+++ b/FAQ
@@ -378,8 +378,10 @@ to pppd when using PAP authentication so that it can select the
appropriate secret from /etc/ppp/pap-secrets.
Microsoft also has a variant of CHAP which uses a different hashing
-arrangement from normal CHAP. There is a client-side implementation
-of Microsoft's CHAP in ppp-2.3; see README.MSCHAP80.
+arrangement from normal CHAP. There is a client-side (authenticatee)
+implementation of Microsoft's CHAP in ppp-2.3; see README.MSCHAP80.
+In ppp-2.4.2, server-side (authenticator) support was added as well as
+support for Microsoft CHAP v2; see README.MSCHAP81.
------------------------------------------------------------------------