2 * rlm_eap_ttls.c contains the interfaces that are called from eap
6 * This program is free software; you can redistribute it and/or modify
7 * it under the terms of the GNU General Public License as published by
8 * the Free Software Foundation; either version 2 of the License, or
9 * (at your option) any later version.
11 * This program is distributed in the hope that it will be useful,
12 * but WITHOUT ANY WARRANTY; without even the implied warranty of
13 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
14 * GNU General Public License for more details.
16 * You should have received a copy of the GNU General Public License
17 * along with this program; if not, write to the Free Software
18 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
20 * Copyright 2003 Alan DeKok <aland@freeradius.org>
27 * 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
28 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
30 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
31 * |V M r r r r r r| AVP Length |
32 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
34 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
40 * Verify that the diameter packet is valid.
42 static int diameter_verify(const uint8_t *data, unsigned int data_len)
47 unsigned int data_left = data_len;
49 while (data_left > 0) {
50 rad_assert(data_left <= data_len);
51 memcpy(&attr, data, sizeof(attr));
55 DEBUG2(" rlm_eap_ttls: Non-RADIUS attribute in tunneled authentication is not supported");
59 memcpy(&length, data , sizeof(length));
61 length = ntohl(length);
64 * A "vendor" flag, with a vendor ID of zero,
65 * is equivalent to no vendor. This is stupid.
68 if ((length & (1 << 31)) != 0) {
73 memcpy(&vendor, data, sizeof(vendor));
74 vendor = ntohl(vendor);
77 DEBUG2(" rlm_eap_ttls: Vendor codes larger than 65535 are not supported");
81 attribute = (vendor << 16) | attr;
83 da = dict_attrbyvalue(attribute);
86 * SHOULD check ((length & (1 << 30)) != 0)
87 * for the mandatory bit.
90 DEBUG2(" rlm_eap_ttls: Fatal! Vendor %u, Attribute %u was not found in our dictionary. ",
95 data += 4; /* skip the vendor field */
96 offset += 4; /* offset to value field */
100 * Ignore the M bit. We support all RADIUS attributes...
104 * Get the length. If it's too big, die.
106 length &= 0x00ffffff;
109 * Too short or too long is bad.
113 if (length < offset) {
114 DEBUG2(" rlm_eap_ttls: Tunneled attribute %d is too short (%d)to contain anything useful.", attr, length);
118 if (length > (MAX_STRING_LEN + 8)) {
119 DEBUG2(" rlm_eap_ttls: Tunneled attribute %d is too long (%d) to pack into a RADIUS attribute.", attr, length);
123 if (length > data_left) {
124 DEBUG2(" rlm_eap_ttls: Tunneled attribute %d is longer than room left in the packet (%d > %d).", attr, length, data_left);
129 * Check for broken implementations, which don't
130 * pad the AVP to a 4-octet boundary.
132 if (data_left == length) break;
135 * The length does NOT include the padding, so
136 * we've got to account for it here by rounding up
137 * to the nearest 4-byte boundary.
143 * If the rest of the diameter packet is larger than
144 * this attribute, continue.
146 * Otherwise, if the attribute over-flows the end
147 * of the packet, die.
149 if (data_left < length) {
150 DEBUG2(" rlm_eap_ttls: ERROR! Diameter attribute overflows packet!");
155 * Check again for equality, now that we're padded
156 * length to a multiple of 4 octets.
158 if (data_left == length) break;
161 * data_left > length, continue.
164 data += length - offset;
168 * We got this far. It looks OK.
175 * Convert diameter attributes to our VALUE_PAIR's
177 static VALUE_PAIR *diameter2vp(SSL *ssl,
178 const uint8_t *data, unsigned int data_len)
184 unsigned int data_left = data_len;
185 VALUE_PAIR *first = NULL;
186 VALUE_PAIR **last = &first;
189 while (data_left > 0) {
190 rad_assert(data_left <= data_len);
191 memcpy(&attr, data, sizeof(attr));
195 memcpy(&length, data, sizeof(length));
197 length = ntohl(length);
200 * Ignore the M bit. We support all RADIUS attributes...
204 * A "vendor" flag, with a vendor ID of zero,
205 * is equivalent to no vendor. This is stupid.
208 if ((length & (1 << 31)) != 0) {
211 memcpy(&vendor, data, sizeof(vendor));
212 vendor = ntohl(vendor);
214 attr |= (vendor << 16);
216 data += 4; /* skip the vendor field, it's zero */
217 offset += 4; /* offset to value field */
223 length &= 0x00ffffff;
226 * diameter code + length, and it must fit in
229 rad_assert(length <= (offset + MAX_STRING_LEN));
232 * Get the size of the value portion of the
235 size = length - offset;
240 vp = paircreate(attr, PW_TYPE_OCTETS);
242 DEBUG2(" rlm_eap_ttls: Failure in creating VP");
248 * If it's a type from our dictionary, then
249 * we need to put the data in a relevant place.
252 case PW_TYPE_INTEGER:
254 if (size != vp->length) {
255 DEBUG2(" rlm_eap_ttls: Invalid length attribute %d",
260 memcpy(&vp->lvalue, data, vp->length);
263 * Stored in host byte order: change it.
265 vp->lvalue = ntohl(vp->lvalue);
269 if (size != vp->length) {
270 DEBUG2(" rlm_eap_ttls: Invalid length attribute %d",
275 memcpy(&vp->lvalue, data, vp->length);
278 * Stored in network byte order: don't change it.
283 * String, octet, etc. Copy the data from the
284 * value field over verbatim.
286 * FIXME: Ipv6 attributes ?
291 memcpy(vp->strvalue, data, vp->length);
296 * User-Password is NUL padded to a multiple
297 * of 16 bytes. Let's chop it to something
300 * NOTE: This means that the User-Password
301 * attribute CANNOT EVER have embedded zeros in it!
303 switch (vp->attribute) {
304 case PW_USER_PASSWORD:
305 rad_assert(vp->length <= 128); /* RFC requirements */
308 * If the password is exactly 16 octets,
309 * it won't be zero-terminated.
311 vp->strvalue[vp->length] = '\0';
312 vp->length = strlen(vp->strvalue);
316 * Ensure that the client is using the
317 * correct challenge. This weirdness is
318 * to protect against against replay
319 * attacks, where anyone observing the
320 * CHAP exchange could pose as that user,
321 * by simply choosing to use the same
324 * By using a challenge based on
325 * information from the current session,
326 * we can guarantee that the client is
327 * not *choosing* a challenge.
329 * We're a little forgiving in that we
330 * have loose checks on the length, and
331 * we do NOT check the Id (first octet of
332 * the response to the challenge)
334 * But if the client gets the challenge correct,
335 * we're not too worried about the Id.
337 case PW_CHAP_CHALLENGE:
338 case PW_MSCHAP_CHALLENGE:
339 if ((vp->length < 8) ||
341 DEBUG2(" TTLS: Tunneled challenge has invalid length");
347 uint8_t challenge[16];
349 eapttls_gen_challenge(ssl, challenge,
352 for (i = 0; i < vp->length; i++) {
353 if (challenge[i] != vp->strvalue[i]) {
354 DEBUG2(" TTLS: Tunneled challenge is incorrect");
364 } /* switch over checking/re-writing of attributes. */
373 * Catch non-aligned attributes.
375 if (data_left == length) break;
378 * The length does NOT include the padding, so
379 * we've got to account for it here by rounding up
380 * to the nearest 4-byte boundary.
385 rad_assert(data_left >= length);
387 data += length - offset; /* already updated */
391 * We got this far. It looks OK.
397 * Convert VALUE_PAIR's to diameter attributes, and write them
400 * The ONLY VALUE_PAIR's which may be passed to this function
401 * are ones which can go inside of a RADIUS (i.e. diameter)
402 * packet. So no server-configuration attributes, or the like.
404 static int vp2diameter(tls_session_t *tls_session, VALUE_PAIR *first)
407 * RADIUS packets are no more than 4k in size, so if
408 * we've got more than 4k of data to write, it's very
411 uint8_t buffer[4096];
422 for (vp = first; vp != NULL; vp = vp->next) {
424 * Too much data: die.
426 if ((total + vp->length + 12) >= sizeof(buffer)) {
427 DEBUG2(" TTLS output buffer is full!");
432 * Hmm... we don't group multiple EAP-Messages
433 * together. Maybe we should...
437 * Length is no more than 253, due to RADIUS
441 vendor = (vp->attribute >> 16) & 0xffff;
443 attr = vp->attribute & 0xffff;
446 attr = vp->attribute;
450 * Hmm... set the M bit for all attributes?
456 memcpy(p, &attr, sizeof(attr));
460 length += 8; /* includes 8 bytes of attr & length */
463 length += 4; /* include 4 bytes of vendor */
465 length = ntohl(length);
466 memcpy(p, &length, sizeof(length));
470 vendor = ntohl(vendor);
471 memcpy(p, &vendor, sizeof(vendor));
475 length = ntohl(length);
476 memcpy(p, &length, sizeof(length));
482 case PW_TYPE_INTEGER:
484 attr = ntohl(vp->lvalue); /* stored in host order */
485 memcpy(p, &attr, sizeof(attr));
490 attr = vp->lvalue; /* stored in network order */
491 memcpy(p, &attr, sizeof(attr));
498 memcpy(p, vp->strvalue, vp->length);
504 * Skip to the end of the data.
510 * Align the data to a multiple of 4 bytes.
512 if ((total & 0x03) != 0) {
515 length = total & 0x03;
516 for (i = 0; i < length; i++) {
522 } /* loop over the VP's to write. */
525 * Write the data in the buffer to the SSL session.
531 if (debug_flag > 2) {
532 for (i = 0; i < total; i++) {
533 if ((i & 0x0f) == 0) printf(" TTLS tunnel data out %04x: ", i);
535 printf("%02x ", buffer[i]);
537 if ((i & 0x0f) == 0x0f) printf("\n");
539 if ((total & 0x0f) != 0) printf("\n");
543 record_plus(&tls_session->clean_in, buffer, total);
546 * FIXME: Check the return code.
548 tls_handshake_send(tls_session);
558 * Use a reply packet to determine what to do.
560 static int process_reply(EAP_HANDLER *handler, tls_session_t *tls_session,
561 REQUEST *request, RADIUS_PACKET *reply)
563 int rcode = RLM_MODULE_REJECT;
565 ttls_tunnel_t *t = tls_session->opaque;
567 handler = handler; /* -Wunused */
570 * If the response packet was Access-Accept, then
571 * we're OK. If not, die horribly.
573 * FIXME: Take MS-CHAP2-Success attribute, and
574 * tunnel it back to the client, to authenticate
575 * ourselves to the client.
577 * FIXME: If we have an Access-Challenge, then
578 * the Reply-Message is tunneled back to the client.
580 * FIXME: If we have an EAP-Message, then that message
581 * must be tunneled back to the client.
583 * FIXME: If we have an Access-Challenge with a State
584 * attribute, then do we tunnel that to the client, or
585 * keep track of it ourselves?
587 * FIXME: EAP-Messages can only start with 'identity',
588 * NOT 'eap start', so we should check for that....
590 switch (reply->code) {
591 case PW_AUTHENTICATION_ACK:
592 DEBUG2(" TTLS: Got tunneled Access-Accept");
594 rcode = RLM_MODULE_OK;
597 * MS-CHAP2-Success means that we do NOT return
598 * an Access-Accept, but instead tunnel that
599 * attribute to the client, and keep going with
600 * the TTLS session. Once the client accepts
601 * our identity, it will respond with an empty
602 * packet, and we will send EAP-Success.
605 pairmove2(&vp, &reply->vps, PW_MSCHAP2_SUCCESS);
609 * FIXME: Tunneling MS-CHAP2-Success causes
610 * the only client we have access to, to die.
612 * We don't want that...
616 DEBUG2(" TTLS: Got MS-CHAP2-Success, tunneling it to the client in a challenge.");
617 rcode = RLM_MODULE_HANDLED;
618 t->authenticated = TRUE;
620 } else { /* no MS-CHAP2-Success */
622 * Can only have EAP-Message if there's
623 * no MS-CHAP2-Success. (FIXME: EAP-MSCHAP?)
625 * We also do NOT tunnel the EAP-Success
626 * attribute back to the client, as the client
627 * can figure it out, from the non-tunneled
628 * EAP-Success packet.
630 pairmove2(&vp, &reply->vps, PW_EAP_MESSAGE);
634 * If we've been told to use the attributes from
635 * the reply, then do so.
637 * WARNING: This may leak information about the
640 if (t->use_tunneled_reply) {
641 pairadd(&request->reply->vps, reply->vps);
647 * Handle the ACK, by tunneling any necessary reply
648 * VP's back to the client.
651 vp2diameter(tls_session, vp);
657 case PW_AUTHENTICATION_REJECT:
658 DEBUG2(" TTLS: Got tunneled Access-Reject");
659 rcode = RLM_MODULE_REJECT;
663 * Handle Access-Challenge, but only if we
664 * send tunneled reply data. This is because
665 * an Access-Challenge means that we MUST tunnel
666 * a Reply-Message to the client.
668 case PW_ACCESS_CHALLENGE:
669 DEBUG2(" TTLS: Got tunneled Access-Challenge");
672 * Keep the State attribute, if necessary.
674 * Get rid of the old State, too.
677 pairmove2(&t->state, &reply->vps, PW_STATE);
680 * We should really be a bit smarter about this,
681 * and move over only those attributes which
682 * are relevant to the authentication request,
683 * but that's a lot more work, and this "dumb"
684 * method works in 99.9% of the situations.
687 pairmove2(&vp, &reply->vps, PW_EAP_MESSAGE);
690 * There MUST be a Reply-Message in the challenge,
691 * which we tunnel back to the client.
693 * If there isn't one in the reply VP's, then
694 * we MUST create one, with an empty string as
697 pairmove2(&vp, &reply->vps, PW_REPLY_MESSAGE);
700 * Handle the ACK, by tunneling any necessary reply
701 * VP's back to the client.
704 vp2diameter(tls_session, vp);
707 rcode = RLM_MODULE_HANDLED;
711 DEBUG2(" TTLS: Unknown RADIUS packet type %d: rejecting tunneled user", reply->code);
712 rcode = RLM_MODULE_REJECT;
721 * Do post-proxy processing,
723 static int eapttls_postproxy(EAP_HANDLER *handler, void *data)
726 tls_session_t *tls_session = (tls_session_t *) data;
728 DEBUG2(" TTLS: Passing reply from proxy back into the tunnel.");
731 * Process the reply from the home server.
733 rcode = process_reply(handler, tls_session, handler->request,
734 handler->request->proxy_reply);
737 * The proxy code uses the reply from the home server as
738 * the basis for the reply to the NAS. We don't want that,
739 * so we toss it, after we've had our way with it.
741 pairfree(&handler->request->proxy_reply->vps);
744 case RLM_MODULE_REJECT:
745 DEBUG2(" TTLS: Reply was rejected");
748 case RLM_MODULE_HANDLED:
749 DEBUG2(" TTLS: Reply was handled");
750 eaptls_request(handler->eap_ds, tls_session);
754 DEBUG2(" TTLS: Reply was OK");
755 eaptls_success(handler->eap_ds, 0);
756 eaptls_gen_mppe_keys(&handler->request->reply->vps,
758 "ttls keying material");
762 DEBUG2(" TTLS: Reply was unknown.");
766 eaptls_fail(handler->eap_ds, 0);
772 * Process the "diameter" contents of the tunneled data.
774 int eapttls_process(EAP_HANDLER *handler, tls_session_t *tls_session)
777 int rcode = PW_AUTHENTICATION_REJECT;
782 unsigned int data_len;
784 REQUEST *request = handler->request;
787 * Grab the dirty data, and copy it to our buffer.
789 * I *really* don't like these 'record_t' things...
791 data_len = record_minus(&tls_session->dirty_in, buffer, sizeof(buffer));
795 * Write the data from the dirty buffer (i.e. packet
796 * data) into the buffer which we will give to SSL for
799 * Some of this code COULD technically go into the TLS
800 * module, in eaptls_process(), where it returns EAPTLS_OK.
802 * Similarly, the writing of data to the SSL context could
805 BIO_write(tls_session->into_ssl, buffer, data_len);
806 record_init(&tls_session->clean_out);
809 * Read (and decrypt) the tunneled data from the SSL session,
810 * and put it into the decrypted data buffer.
812 err = SSL_read(tls_session->ssl, tls_session->clean_out.data,
813 sizeof(tls_session->clean_out.data));
816 * FIXME: Call SSL_get_error() to see what went
819 radlog(L_INFO, "rlm_eap_ttls: SSL_read Error");
820 return PW_AUTHENTICATION_REJECT;
823 t = (ttls_tunnel_t *) tls_session->opaque;
826 * If there's no data, maybe this is an ACK to an
830 if (t->authenticated) {
831 DEBUG2(" TTLS: Got ACK, and the user was already authenticated.");
832 return PW_AUTHENTICATION_ACK;
833 } /* else no session, no data, die. */
836 * FIXME: Call SSL_get_error() to see what went
839 radlog(L_INFO, "rlm_eap_ttls: SSL_read Error");
840 return PW_AUTHENTICATION_REJECT;
843 data_len = tls_session->clean_out.used = err;
844 data = tls_session->clean_out.data;
847 if (debug_flag > 2) {
850 for (i = 0; i < data_len; i++) {
851 if ((i & 0x0f) == 0) printf(" TTLS tunnel data in %04x: ", i);
853 printf("%02x ", data[i]);
855 if ((i & 0x0f) == 0x0f) printf("\n");
857 if ((data_len & 0x0f) != 0) printf("\n");
861 if (!diameter_verify(data, data_len)) {
862 return PW_AUTHENTICATION_REJECT;
866 * Allocate a fake REQUEST structe.
868 fake = request_alloc_fake(request);
870 rad_assert(fake->packet->vps == NULL);
873 * Add the tunneled attributes to the fake request.
875 fake->packet->vps = diameter2vp(tls_session->ssl, data, data_len);
876 if (!fake->packet->vps) {
877 return PW_AUTHENTICATION_REJECT;
881 * Tell the request that it's a fake one.
883 vp = pairmake("Freeradius-Proxied-To", "127.0.0.1", T_OP_EQ);
885 pairadd(&fake->packet->vps, vp);
889 if (debug_flag > 0) {
890 printf(" TTLS: Got tunneled request\n");
892 for (vp = fake->packet->vps; vp != NULL; vp = vp->next) {
893 putchar('\t');vp_print(stdout, vp);putchar('\n');
899 * Update other items in the REQUEST data structure.
901 fake->username = pairfind(fake->packet->vps, PW_USER_NAME);
902 fake->password = pairfind(fake->packet->vps, PW_PASSWORD);
905 * No User-Name, try to create one from stored data.
907 if (!fake->username) {
909 * No User-Name in the stored data, look for
910 * an EAP-Identity, and pull it out of there.
913 vp = pairfind(fake->packet->vps, PW_EAP_MESSAGE);
915 (vp->length >= EAP_HEADER_LEN + 2) &&
916 (vp->strvalue[0] == PW_EAP_RESPONSE) &&
917 (vp->strvalue[EAP_HEADER_LEN] == PW_EAP_IDENTITY) &&
918 (vp->strvalue[EAP_HEADER_LEN + 1] != 0)) {
920 * Create & remember a User-Name
922 t->username = pairmake("User-Name", "", T_OP_EQ);
923 rad_assert(t->username != NULL);
925 memcpy(t->username->strvalue, vp->strvalue + 5,
927 t->username->length = vp->length - 5;
928 t->username->strvalue[t->username->length] = 0;
930 DEBUG2(" TTLS: Got tunneled identity of %s",
931 t->username->strvalue);
934 * If there's a default EAP type,
937 if (t->default_eap_type != 0) {
938 DEBUG2(" TTLS: Setting default EAP type for tunneled EAP session.");
939 vp = paircreate(PW_EAP_TYPE,
941 rad_assert(vp != NULL);
942 vp->lvalue = t->default_eap_type;
943 pairadd(&fake->config_items, vp);
948 * Don't reject the request outright,
949 * as it's permitted to do EAP without
952 DEBUG2(" rlm_eap_ttls: WARNING! No EAP-Identity found to start EAP conversation.");
954 } /* else there WAS a t->username */
957 vp = paircopy(t->username);
958 pairadd(&fake->packet->vps, vp);
959 fake->username = pairfind(fake->packet->vps, PW_USER_NAME);
961 } /* else the request ALREADY had a User-Name */
964 * Add the State attribute, too, if it exists.
967 DEBUG2(" TTLS: Adding old state with %02x %02x",
968 t->state->strvalue[0], t->state->strvalue[1]);
969 vp = paircopy(t->state);
970 if (vp) pairadd(&fake->packet->vps, vp);
974 * If this is set, we copy SOME of the request attributes
975 * from outside of the tunnel to inside of the tunnel.
977 * We copy ONLY those attributes which do NOT already
978 * exist in the tunneled request.
980 if (t->copy_request_to_tunnel) {
983 for (vp = request->packet->vps; vp != NULL; vp = vp->next) {
985 * The attribute is a server-side thingy,
988 if ((vp->attribute > 255) &&
989 (((vp->attribute >> 16) & 0xffff) == 0)) {
994 * The outside attribute is already in the
995 * tunnel, don't copy it.
997 * This works for BOTH attributes which
998 * are originally in the tunneled request,
999 * AND attributes which are copied there
1002 if (pairfind(fake->packet->vps, vp->attribute)) {
1007 * Some attributes are handled specially.
1009 switch (vp->attribute) {
1011 * NEVER copy Message-Authenticator,
1012 * EAP-Message, or State. They're
1013 * only for outside of the tunnel.
1016 case PW_USER_PASSWORD:
1017 case PW_CHAP_PASSWORD:
1018 case PW_CHAP_CHALLENGE:
1019 case PW_PROXY_STATE:
1020 case PW_MESSAGE_AUTHENTICATOR:
1021 case PW_EAP_MESSAGE:
1027 * By default, copy it over.
1034 * Don't copy from the head, we've already
1037 copy = paircopy2(vp, vp->attribute);
1038 pairadd(&fake->packet->vps, copy);
1043 if (debug_flag > 0) {
1044 printf(" TTLS: Sending tunneled request\n");
1046 for (vp = fake->packet->vps; vp != NULL; vp = vp->next) {
1047 putchar('\t');vp_print(stdout, vp);putchar('\n');
1053 * Call authentication recursively, which will
1054 * do PAP, CHAP, MS-CHAP, etc.
1056 rad_authenticate(fake);
1059 * Note that we don't do *anything* with the reply
1063 if (debug_flag > 0) {
1064 printf(" TTLS: Got tunneled reply RADIUS code %d\n",
1067 for (vp = fake->reply->vps; vp != NULL; vp = vp->next) {
1068 putchar('\t');vp_print(stdout, vp);putchar('\n');
1074 * Decide what to do with the reply.
1076 switch (fake->reply->code) {
1077 case 0: /* No reply code, must be proxied... */
1078 vp = pairfind(fake->config_items, PW_PROXY_TO_REALM);
1080 eap_tunnel_data_t *tunnel;
1081 DEBUG2(" TTLS: Tunneled authentication will be proxied to %s", vp->strvalue);
1084 * Tell the original request that it's going
1087 pairmove2(&(request->config_items),
1088 &(fake->config_items),
1092 * Seed the proxy packet with the
1095 rad_assert(request->proxy == NULL);
1096 request->proxy = fake->packet;
1097 fake->packet = NULL;
1100 * Set up the callbacks for the tunnel
1102 tunnel = rad_malloc(sizeof(*tunnel));
1103 memset(tunnel, 0, sizeof(*tunnel));
1105 tunnel->tls_session = tls_session;
1106 tunnel->callback = eapttls_postproxy;
1109 * Associate the callback with the request.
1111 rcode = request_data_add(request,
1113 REQUEST_DATA_EAP_TUNNEL_CALLBACK,
1115 rad_assert(rcode == 0);
1118 * Didn't authenticate the packet, but
1119 * we're proxying it.
1121 rcode = RLM_MODULE_UPDATED;
1124 DEBUG2(" TTLS: No tunneled reply was found for request %d , and the request was not proxied: rejecting the user.",
1126 rcode = RLM_MODULE_REJECT;
1131 rcode = process_reply(handler, tls_session, request,
1136 request_free(&fake);