Replaced references to MS-CHAP-Success with MS2-CHAP-Success
authorHerwin Weststrate <herwin@quarantainenet.nl>
Wed, 11 Jun 2014 14:45:14 +0000 (16:45 +0200)
committerArran Cudbard-Bell <a.cudbardb@freeradius.org>
Fri, 13 Jun 2014 13:57:46 +0000 (14:57 +0100)
The first attribute doesn't exist.

src/modules/rlm_eap/types/rlm_eap_mschapv2/rlm_eap_mschapv2.c
src/modules/rlm_eap/types/rlm_eap_peap/peap.c

index 6538d4a..13beb38 100644 (file)
@@ -322,7 +322,7 @@ static int CC_HINT(nonnull) mschap_postproxy(eap_handler_t *handler, UNUSED void
         *      No response, die.
         */
        if (!response) {
-               REDEBUG("Proxied reply contained no MS-CHAP-Success or MS-CHAP-Error");
+               REDEBUG("Proxied reply contained no MS-CHAP2-Success or MS-CHAP-Error");
                return 0;
        }
 
@@ -722,7 +722,7 @@ packet_ready:
         *      No response, die.
         */
        if (!response) {
-               REDEBUG("No MS-CHAP-Success or MS-CHAP-Error was found");
+               REDEBUG("No MS-CHAP2-Success or MS-CHAP-Error was found");
                return 0;
        }
 
index ecd977a..1f7bbb1 100644 (file)
@@ -497,7 +497,7 @@ static int CC_HINT(nonnull) process_reply(eap_handler_t *handler, tls_session_t
 
                /*
                 *      Handle EAP-MSCHAP-V2, where Access-Accept's
-                *      from the home server may contain MS-CHAP-Success,
+                *      from the home server may contain MS-CHAP2-Success,
                 *      which the module turns into challenges, so that
                 *      the client may respond to the challenge with
                 *      an "ack" packet.