From: Alan T. DeKok <aland@freeradius.org>
Date: Tue, 20 Sep 2016 11:46:13 +0000 (-0400)
Subject: remove unnecessary FIXMEs
X-Git-Tag: release_3_0_12~50
X-Git-Url: http://www.project-moonshot.org/gitweb/?p=freeradius.git;a=commitdiff_plain;h=594e07c47e44c1e21d35a96db6b271cafac68a70

remove unnecessary FIXMEs
---

diff --git a/src/modules/rlm_eap/types/rlm_eap_fast/eap_fast.c b/src/modules/rlm_eap/types/rlm_eap_fast/eap_fast.c
index 21cf999..f774883 100644
--- a/src/modules/rlm_eap/types/rlm_eap_fast/eap_fast.c
+++ b/src/modules/rlm_eap/types/rlm_eap_fast/eap_fast.c
@@ -772,20 +772,6 @@ static rlm_rcode_t CC_HINT(nonnull) process_reply( eap_handler_t *eap_session,
 	 * If the response packet was Access-Accept, then
 	 * we're OK.  If not, die horribly.
 	 *
-	 * FIXME: Take MS-CHAP2-Success attribute, and
-	 * tunnel it back to the client, to authenticate
-	 * ourselves to the client.
-	 *
-	 * FIXME: If we have an Access-Challenge, then
-	 * the Reply-Message is tunneled back to the client.
-	 *
-	 * FIXME: If we have an EAP-Message, then that message
-	 * must be tunneled back to the client.
-	 *
-	 * FIXME: If we have an Access-Challenge with a State
-	 * attribute, then do we tunnel that to the client, or
-	 * keep track of it ourselves?
-	 *
 	 * FIXME: EAP-Messages can only start with 'identity',
 	 * NOT 'eap start', so we should check for that....
 	 */