X-Git-Url: http://git.ozlabs.org/?p=ppp.git;a=blobdiff_plain;f=FAQ;fp=FAQ;h=cb42c6bc67492e0a10001859b9ea1fa13f48b360;hp=ef6dd73b29f19d440895b7c29a58053b4f2fda77;hb=0816630b7e90b23792599af619d6950841891b9b;hpb=6815640f313fe730642df94144180702d29ef8a1

diff --git a/FAQ b/FAQ
index ef6dd73..cb42c6b 100644
--- a/FAQ
+++ b/FAQ
@@ -370,13 +370,9 @@ the server.  Thus, it may be necessary to use the `remotename' option
 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 they apparently think is
-more secure than standard CHAP because they don't store secrets in
-clear text on the server.  However, a bogus client only needs to know
-the encrypted secret to gain access, so the only extra security is
-that the bogus client would need to run something other than Windows.
-There is a client-side implementation of Microsoft's CHAP in ppp-2.3;
-see README.MSCHAP80.
+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.
 
 
 ------------------------------------------------------------------------