Use the correct macro for INFO debugging

This is all documented in great detail in log.h

diff --git a/src/modules/rlm_eap/types/rlm_eap_peap/peap.c b/src/modules/rlm_eap/types/rlm_eap_peap/peap.c
index 3f575e4ba6fd2ecf727ed8fe8fbb9d7666f26315..bdb11d615676d49cb5855ad856f61e21f98a3ca0 100644 (file)
--- a/src/modules/rlm_eap/types/rlm_eap_peap/peap.c
+++ b/src/modules/rlm_eap/types/rlm_eap_peap/peap.c
@@ -872,16 +872,15 @@ rlm_rcode_t eappeap_process(eap_handler_t *handler, tls_session_t *tls_session)
                return RLM_MODULE_REJECT;
 
        /*
-        *      Damned if I know why the clients continue sending EAP
-        *      packets after we told them to f*ck off.
+        *      Supplicant ACKs our failure.
         */
        case PEAP_STATUS_SENT_TLV_FAILURE:
                RINDENT();
-               RINFO("The users session was previously rejected: returning reject (again.)");
-               RINFO("This means you need to read the PREVIOUS messages in the debug output");
-               RINFO("to find out the reason why the user was rejected");
-               RINFO("Look for \"reject\" or \"fail\".  Those earlier messages will tell you");
-               RINFO("what went wrong, and how to fix the problem");
+               RIDEBUG("The users session was previously rejected: returning reject (again.)");
+               RIDEBUG("This means you need to read the PREVIOUS messages in the debug output");
+               RIDEBUG("to find out the reason why the user was rejected");
+               RIDEBUG("Look for \"reject\" or \"fail\".  Those earlier messages will tell you");
+               RIDEBUG("what went wrong, and how to fix the problem");
                REXDENT();
 
                return RLM_MODULE_REJECT;