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., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
20 * Copyright 2003 Alan DeKok <aland@freeradius.org>
26 * 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
27 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
29 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
30 * |V M r r r r r r| AVP Length |
31 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
33 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
39 * Verify that the diameter packet is valid.
41 static int diameter_verify(const uint8_t *data, unsigned int data_len)
46 unsigned int data_left = data_len;
48 while (data_left > 0) {
49 rad_assert(data_left <= data_len);
50 memcpy(&attr, data, sizeof(attr));
54 DEBUG2(" rlm_eap_ttls: Non-RADIUS attribute in tunneled authentication is not supported");
58 memcpy(&length, data , sizeof(length));
60 length = ntohl(length);
63 * A "vendor" flag, with a vendor ID of zero,
64 * is equivalent to no vendor. This is stupid.
67 if ((length & (1 << 31)) != 0) {
72 memcpy(&vendor, data, sizeof(vendor));
73 vendor = ntohl(vendor);
76 DEBUG2(" rlm_eap_ttls: Vendor codes larger than 65535 are not supported");
80 attribute = (vendor << 16) | attr;
82 da = dict_attrbyvalue(attribute);
85 * SHOULD check ((length & (1 << 30)) != 0)
86 * for the mandatory bit.
89 DEBUG2(" rlm_eap_ttls: Fatal! Vendor %u, Attribute %u was not found in our dictionary. ",
94 data += 4; /* skip the vendor field */
95 offset += 4; /* offset to value field */
99 * Ignore the M bit. We support all RADIUS attributes...
103 * Get the length. If it's too big, die.
105 length &= 0x00ffffff;
108 * Too short or too long is bad.
112 if (length < offset) {
113 DEBUG2(" rlm_eap_ttls: Tunneled attribute %d is too short (%d)to contain anything useful.", attr, length);
117 if (length > (MAX_STRING_LEN + 8)) {
118 DEBUG2(" rlm_eap_ttls: Tunneled attribute %d is too long (%d) to pack into a RADIUS attribute.", attr, length);
122 if (length > data_left) {
123 DEBUG2(" rlm_eap_ttls: Tunneled attribute %d is longer than room left in the packet (%d > %d).", attr, length, data_left);
128 * Check for broken implementations, which don't
129 * pad the AVP to a 4-octet boundary.
131 if (data_left == length) break;
134 * The length does NOT include the padding, so
135 * we've got to account for it here by rounding up
136 * to the nearest 4-byte boundary.
142 * If the rest of the diameter packet is larger than
143 * this attribute, continue.
145 * Otherwise, if the attribute over-flows the end
146 * of the packet, die.
148 if (data_left < length) {
149 DEBUG2(" rlm_eap_ttls: ERROR! Diameter attribute overflows packet!");
154 * Check again for equality, now that we're padded
155 * length to a multiple of 4 octets.
157 if (data_left == length) break;
160 * data_left > length, continue.
163 data += length - offset;
167 * We got this far. It looks OK.
174 * Convert diameter attributes to our VALUE_PAIR's
176 static VALUE_PAIR *diameter2vp(SSL *ssl,
177 const uint8_t *data, unsigned int data_len)
183 unsigned int data_left = data_len;
184 VALUE_PAIR *first = NULL;
185 VALUE_PAIR **last = &first;
188 while (data_left > 0) {
189 rad_assert(data_left <= data_len);
190 memcpy(&attr, data, sizeof(attr));
194 memcpy(&length, data, sizeof(length));
196 length = ntohl(length);
199 * Ignore the M bit. We support all RADIUS attributes...
203 * A "vendor" flag, with a vendor ID of zero,
204 * is equivalent to no vendor. This is stupid.
207 if ((length & (1 << 31)) != 0) {
210 memcpy(&vendor, data, sizeof(vendor));
211 vendor = ntohl(vendor);
213 attr |= (vendor << 16);
215 data += 4; /* skip the vendor field, it's zero */
216 offset += 4; /* offset to value field */
222 length &= 0x00ffffff;
225 * diameter code + length, and it must fit in
228 rad_assert(length <= (offset + MAX_STRING_LEN));
231 * Get the size of the value portion of the
234 size = length - offset;
239 vp = paircreate(attr, PW_TYPE_OCTETS);
241 DEBUG2(" rlm_eap_ttls: Failure in creating VP");
247 * If it's a type from our dictionary, then
248 * we need to put the data in a relevant place.
251 case PW_TYPE_INTEGER:
253 if (size != vp->length) {
254 DEBUG2(" rlm_eap_ttls: Invalid length attribute %d",
259 memcpy(&vp->lvalue, data, vp->length);
262 * Stored in host byte order: change it.
264 vp->lvalue = ntohl(vp->lvalue);
268 if (size != vp->length) {
269 DEBUG2(" rlm_eap_ttls: Invalid length attribute %d",
274 memcpy(&vp->lvalue, data, vp->length);
277 * Stored in network byte order: don't change it.
282 * String, octet, etc. Copy the data from the
283 * value field over verbatim.
285 * FIXME: Ipv6 attributes ?
290 memcpy(vp->vp_strvalue, data, vp->length);
295 * User-Password is NUL padded to a multiple
296 * of 16 bytes. Let's chop it to something
299 * NOTE: This means that the User-Password
300 * attribute CANNOT EVER have embedded zeros in it!
302 switch (vp->attribute) {
303 case PW_USER_PASSWORD:
304 rad_assert(vp->length <= 128); /* RFC requirements */
307 * If the password is exactly 16 octets,
308 * it won't be zero-terminated.
310 vp->vp_strvalue[vp->length] = '\0';
311 vp->length = strlen(vp->vp_strvalue);
315 * Ensure that the client is using the
316 * correct challenge. This weirdness is
317 * to protect against against replay
318 * attacks, where anyone observing the
319 * CHAP exchange could pose as that user,
320 * by simply choosing to use the same
323 * By using a challenge based on
324 * information from the current session,
325 * we can guarantee that the client is
326 * not *choosing* a challenge.
328 * We're a little forgiving in that we
329 * have loose checks on the length, and
330 * we do NOT check the Id (first octet of
331 * the response to the challenge)
333 * But if the client gets the challenge correct,
334 * we're not too worried about the Id.
336 case PW_CHAP_CHALLENGE:
337 case PW_MSCHAP_CHALLENGE:
338 if ((vp->length < 8) ||
340 DEBUG2(" TTLS: Tunneled challenge has invalid length");
346 uint8_t challenge[16];
348 eapttls_gen_challenge(ssl, challenge,
351 for (i = 0; i < vp->length; i++) {
352 if (challenge[i] != vp->vp_strvalue[i]) {
353 DEBUG2(" TTLS: Tunneled challenge is incorrect");
363 } /* switch over checking/re-writing of attributes. */
372 * Catch non-aligned attributes.
374 if (data_left == length) break;
377 * The length does NOT include the padding, so
378 * we've got to account for it here by rounding up
379 * to the nearest 4-byte boundary.
384 rad_assert(data_left >= length);
386 data += length - offset; /* already updated */
390 * We got this far. It looks OK.
396 * Convert VALUE_PAIR's to diameter attributes, and write them
399 * The ONLY VALUE_PAIR's which may be passed to this function
400 * are ones which can go inside of a RADIUS (i.e. diameter)
401 * packet. So no server-configuration attributes, or the like.
403 static int vp2diameter(tls_session_t *tls_session, VALUE_PAIR *first)
406 * RADIUS packets are no more than 4k in size, so if
407 * we've got more than 4k of data to write, it's very
410 uint8_t buffer[4096];
421 for (vp = first; vp != NULL; vp = vp->next) {
423 * Too much data: die.
425 if ((total + vp->length + 12) >= sizeof(buffer)) {
426 DEBUG2(" TTLS output buffer is full!");
431 * Hmm... we don't group multiple EAP-Messages
432 * together. Maybe we should...
436 * Length is no more than 253, due to RADIUS
440 vendor = (vp->attribute >> 16) & 0xffff;
442 attr = vp->attribute & 0xffff;
445 attr = vp->attribute;
449 * Hmm... set the M bit for all attributes?
455 memcpy(p, &attr, sizeof(attr));
459 length += 8; /* includes 8 bytes of attr & length */
462 length += 4; /* include 4 bytes of vendor */
464 length = ntohl(length);
465 memcpy(p, &length, sizeof(length));
469 vendor = ntohl(vendor);
470 memcpy(p, &vendor, sizeof(vendor));
474 length = ntohl(length);
475 memcpy(p, &length, sizeof(length));
481 case PW_TYPE_INTEGER:
483 attr = ntohl(vp->lvalue); /* stored in host order */
484 memcpy(p, &attr, sizeof(attr));
489 attr = vp->lvalue; /* stored in network order */
490 memcpy(p, &attr, sizeof(attr));
497 memcpy(p, vp->vp_strvalue, vp->length);
503 * Skip to the end of the data.
509 * Align the data to a multiple of 4 bytes.
511 if ((total & 0x03) != 0) {
514 length = 4 - (total & 0x03);
515 for (i = 0; i < length; i++) {
521 } /* loop over the VP's to write. */
524 * Write the data in the buffer to the SSL session.
530 if (debug_flag > 2) {
531 for (i = 0; i < total; i++) {
532 if ((i & 0x0f) == 0) printf(" TTLS tunnel data out %04x: ", i);
534 printf("%02x ", buffer[i]);
536 if ((i & 0x0f) == 0x0f) printf("\n");
538 if ((total & 0x0f) != 0) printf("\n");
542 (tls_session->record_plus)(&tls_session->clean_in, buffer, total);
545 * FIXME: Check the return code.
547 tls_handshake_send(tls_session);
557 * Use a reply packet to determine what to do.
559 static int process_reply(EAP_HANDLER *handler, tls_session_t *tls_session,
560 REQUEST *request, RADIUS_PACKET *reply)
562 int rcode = RLM_MODULE_REJECT;
564 ttls_tunnel_t *t = tls_session->opaque;
566 handler = handler; /* -Wunused */
569 * If the response packet was Access-Accept, then
570 * we're OK. If not, die horribly.
572 * FIXME: Take MS-CHAP2-Success attribute, and
573 * tunnel it back to the client, to authenticate
574 * ourselves to the client.
576 * FIXME: If we have an Access-Challenge, then
577 * the Reply-Message is tunneled back to the client.
579 * FIXME: If we have an EAP-Message, then that message
580 * must be tunneled back to the client.
582 * FIXME: If we have an Access-Challenge with a State
583 * attribute, then do we tunnel that to the client, or
584 * keep track of it ourselves?
586 * FIXME: EAP-Messages can only start with 'identity',
587 * NOT 'eap start', so we should check for that....
589 switch (reply->code) {
590 case PW_AUTHENTICATION_ACK:
591 DEBUG2(" TTLS: Got tunneled Access-Accept");
593 rcode = RLM_MODULE_OK;
596 * MS-CHAP2-Success means that we do NOT return
597 * an Access-Accept, but instead tunnel that
598 * attribute to the client, and keep going with
599 * the TTLS session. Once the client accepts
600 * our identity, it will respond with an empty
601 * packet, and we will send EAP-Success.
604 pairmove2(&vp, &reply->vps, PW_MSCHAP2_SUCCESS);
608 * FIXME: Tunneling MS-CHAP2-Success causes
609 * the only client we have access to, to die.
611 * We don't want that...
615 DEBUG2(" TTLS: Got MS-CHAP2-Success, tunneling it to the client in a challenge.");
616 rcode = RLM_MODULE_HANDLED;
617 t->authenticated = TRUE;
619 } else { /* no MS-CHAP2-Success */
621 * Can only have EAP-Message if there's
622 * no MS-CHAP2-Success. (FIXME: EAP-MSCHAP?)
624 * We also do NOT tunnel the EAP-Success
625 * attribute back to the client, as the client
626 * can figure it out, from the non-tunneled
627 * EAP-Success packet.
629 pairmove2(&vp, &reply->vps, PW_EAP_MESSAGE);
634 * Handle the ACK, by tunneling any necessary reply
635 * VP's back to the client.
638 vp2diameter(tls_session, vp);
643 * If we've been told to use the attributes from
644 * the reply, then do so.
646 * WARNING: This may leak information about the
649 if (t->use_tunneled_reply) {
650 pairdelete(&reply->vps, PW_PROXY_STATE);
651 pairadd(&request->reply->vps, reply->vps);
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_INVALID;
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;
729 DEBUG2(" TTLS: Passing reply from proxy back into the tunnel.");
732 * If there was a fake request associated with the proxied
733 * request, do more processing of it.
735 fake = (REQUEST *) request_data_get(handler->request,
736 handler->request->proxy,
737 REQUEST_DATA_EAP_MSCHAP_TUNNEL_CALLBACK);
740 * Do the callback, if it exists, and if it was a success.
742 if (fake && (handler->request->proxy_reply->code == PW_AUTHENTICATION_ACK)) {
744 REQUEST *request = handler->request;
749 rad_assert(fake->packet == NULL);
750 fake->packet = request->proxy;
751 request->proxy = NULL;
753 rad_assert(fake->reply == NULL);
754 fake->reply = request->proxy_reply;
755 request->proxy_reply = NULL;
758 * Perform a post-auth stage for the tunneled
761 fake->options &= ~RAD_REQUEST_OPTION_PROXY_EAP;
762 rcode = rad_postauth(fake);
763 DEBUG2(" POST-AUTH %d", rcode);
766 if (debug_flag > 0) {
767 printf(" TTLS: Final reply from tunneled session code %d\n",
770 for (vp = fake->reply->vps; vp != NULL; vp = vp->next) {
771 putchar('\t');vp_print(stdout, vp);putchar('\n');
779 request->proxy = fake->packet;
781 request->proxy_reply = fake->reply;
785 * And we're done with this request.
789 case RLM_MODULE_FAIL:
791 eaptls_fail(handler->eap_ds, 0);
795 default: /* Don't Do Anything */
796 DEBUG2(" TTLS: Got reply %d",
797 request->proxy_reply->code);
801 request_free(&fake); /* robust if fake == NULL */
804 * Process the reply from the home server.
806 rcode = process_reply(handler, tls_session, handler->request,
807 handler->request->proxy_reply);
810 * The proxy code uses the reply from the home server as
811 * the basis for the reply to the NAS. We don't want that,
812 * so we toss it, after we've had our way with it.
814 pairfree(&handler->request->proxy_reply->vps);
817 case RLM_MODULE_REJECT:
818 DEBUG2(" TTLS: Reply was rejected");
821 case RLM_MODULE_HANDLED:
822 DEBUG2(" TTLS: Reply was handled");
823 eaptls_request(handler->eap_ds, tls_session);
827 DEBUG2(" TTLS: Reply was OK");
828 eaptls_success(handler->eap_ds, 0);
829 eaptls_gen_mppe_keys(&handler->request->reply->vps,
831 "ttls keying material");
835 DEBUG2(" TTLS: Reply was unknown.");
839 eaptls_fail(handler->eap_ds, 0);
847 static void my_request_free(void *data)
849 REQUEST *request = (REQUEST *)data;
851 request_free(&request);
856 * Process the "diameter" contents of the tunneled data.
858 int eapttls_process(EAP_HANDLER *handler, tls_session_t *tls_session)
861 int rcode = PW_AUTHENTICATION_REJECT;
866 unsigned int data_len;
868 REQUEST *request = handler->request;
871 * Grab the dirty data, and copy it to our buffer.
873 * I *really* don't like these 'record_t' things...
875 data_len = (tls_session->record_minus)(&tls_session->dirty_in, buffer, sizeof(buffer));
879 * Write the data from the dirty buffer (i.e. packet
880 * data) into the buffer which we will give to SSL for
883 * Some of this code COULD technically go into the TLS
884 * module, in eaptls_process(), where it returns EAPTLS_OK.
886 * Similarly, the writing of data to the SSL context could
889 BIO_write(tls_session->into_ssl, buffer, data_len);
890 (tls_session->record_init)(&tls_session->clean_out);
893 * Read (and decrypt) the tunneled data from the SSL session,
894 * and put it into the decrypted data buffer.
896 err = SSL_read(tls_session->ssl, tls_session->clean_out.data,
897 sizeof(tls_session->clean_out.data));
900 * FIXME: Call SSL_get_error() to see what went
903 radlog(L_INFO, "rlm_eap_ttls: SSL_read Error");
904 return PW_AUTHENTICATION_REJECT;
907 t = (ttls_tunnel_t *) tls_session->opaque;
910 * If there's no data, maybe this is an ACK to an
914 if (t->authenticated) {
915 DEBUG2(" TTLS: Got ACK, and the user was already authenticated.");
916 return PW_AUTHENTICATION_ACK;
917 } /* else no session, no data, die. */
920 * FIXME: Call SSL_get_error() to see what went
923 radlog(L_INFO, "rlm_eap_ttls: SSL_read Error");
924 return PW_AUTHENTICATION_REJECT;
927 data_len = tls_session->clean_out.used = err;
928 data = tls_session->clean_out.data;
931 if (debug_flag > 2) {
934 for (i = 0; i < data_len; i++) {
935 if ((i & 0x0f) == 0) printf(" TTLS tunnel data in %04x: ", i);
937 printf("%02x ", data[i]);
939 if ((i & 0x0f) == 0x0f) printf("\n");
941 if ((data_len & 0x0f) != 0) printf("\n");
945 if (!diameter_verify(data, data_len)) {
946 return PW_AUTHENTICATION_REJECT;
950 * Allocate a fake REQUEST structe.
952 fake = request_alloc_fake(request);
954 rad_assert(fake->packet->vps == NULL);
957 * Add the tunneled attributes to the fake request.
959 fake->packet->vps = diameter2vp(tls_session->ssl, data, data_len);
960 if (!fake->packet->vps) {
961 return PW_AUTHENTICATION_REJECT;
965 * Tell the request that it's a fake one.
967 vp = pairmake("Freeradius-Proxied-To", "127.0.0.1", T_OP_EQ);
969 pairadd(&fake->packet->vps, vp);
973 if (debug_flag > 0) {
974 printf(" TTLS: Got tunneled request\n");
976 for (vp = fake->packet->vps; vp != NULL; vp = vp->next) {
977 putchar('\t');vp_print(stdout, vp);putchar('\n');
983 * Update other items in the REQUEST data structure.
985 fake->username = pairfind(fake->packet->vps, PW_USER_NAME);
986 fake->password = pairfind(fake->packet->vps, PW_PASSWORD);
989 * No User-Name, try to create one from stored data.
991 if (!fake->username) {
993 * No User-Name in the stored data, look for
994 * an EAP-Identity, and pull it out of there.
997 vp = pairfind(fake->packet->vps, PW_EAP_MESSAGE);
999 (vp->length >= EAP_HEADER_LEN + 2) &&
1000 (vp->vp_strvalue[0] == PW_EAP_RESPONSE) &&
1001 (vp->vp_strvalue[EAP_HEADER_LEN] == PW_EAP_IDENTITY) &&
1002 (vp->vp_strvalue[EAP_HEADER_LEN + 1] != 0)) {
1004 * Create & remember a User-Name
1006 t->username = pairmake("User-Name", "", T_OP_EQ);
1007 rad_assert(t->username != NULL);
1009 memcpy(t->username->vp_strvalue, vp->vp_strvalue + 5,
1011 t->username->length = vp->length - 5;
1012 t->username->vp_strvalue[t->username->length] = 0;
1014 DEBUG2(" TTLS: Got tunneled identity of %s",
1015 t->username->vp_strvalue);
1018 * If there's a default EAP type,
1021 if (t->default_eap_type != 0) {
1022 DEBUG2(" TTLS: Setting default EAP type for tunneled EAP session.");
1023 vp = paircreate(PW_EAP_TYPE,
1025 rad_assert(vp != NULL);
1026 vp->lvalue = t->default_eap_type;
1027 pairadd(&fake->config_items, vp);
1032 * Don't reject the request outright,
1033 * as it's permitted to do EAP without
1036 DEBUG2(" rlm_eap_ttls: WARNING! No EAP-Identity found to start EAP conversation.");
1038 } /* else there WAS a t->username */
1041 vp = paircopy(t->username);
1042 pairadd(&fake->packet->vps, vp);
1043 fake->username = pairfind(fake->packet->vps, PW_USER_NAME);
1045 } /* else the request ALREADY had a User-Name */
1048 * Add the State attribute, too, if it exists.
1051 DEBUG2(" TTLS: Adding old state with %02x %02x",
1052 t->state->vp_strvalue[0], t->state->vp_strvalue[1]);
1053 vp = paircopy(t->state);
1054 if (vp) pairadd(&fake->packet->vps, vp);
1058 * If this is set, we copy SOME of the request attributes
1059 * from outside of the tunnel to inside of the tunnel.
1061 * We copy ONLY those attributes which do NOT already
1062 * exist in the tunneled request.
1064 if (t->copy_request_to_tunnel) {
1067 for (vp = request->packet->vps; vp != NULL; vp = vp->next) {
1069 * The attribute is a server-side thingy,
1072 if ((vp->attribute > 255) &&
1073 (((vp->attribute >> 16) & 0xffff) == 0)) {
1078 * The outside attribute is already in the
1079 * tunnel, don't copy it.
1081 * This works for BOTH attributes which
1082 * are originally in the tunneled request,
1083 * AND attributes which are copied there
1086 if (pairfind(fake->packet->vps, vp->attribute)) {
1091 * Some attributes are handled specially.
1093 switch (vp->attribute) {
1095 * NEVER copy Message-Authenticator,
1096 * EAP-Message, or State. They're
1097 * only for outside of the tunnel.
1100 case PW_USER_PASSWORD:
1101 case PW_CHAP_PASSWORD:
1102 case PW_CHAP_CHALLENGE:
1103 case PW_PROXY_STATE:
1104 case PW_MESSAGE_AUTHENTICATOR:
1105 case PW_EAP_MESSAGE:
1111 * By default, copy it over.
1118 * Don't copy from the head, we've already
1121 copy = paircopy2(vp, vp->attribute);
1122 pairadd(&fake->packet->vps, copy);
1127 if (debug_flag > 0) {
1128 printf(" TTLS: Sending tunneled request\n");
1130 for (vp = fake->packet->vps; vp != NULL; vp = vp->next) {
1131 putchar('\t');vp_print(stdout, vp);putchar('\n');
1137 * Call authentication recursively, which will
1138 * do PAP, CHAP, MS-CHAP, etc.
1140 rad_authenticate(fake);
1143 * Note that we don't do *anything* with the reply
1147 if (debug_flag > 0) {
1148 printf(" TTLS: Got tunneled reply RADIUS code %d\n",
1151 for (vp = fake->reply->vps; vp != NULL; vp = vp->next) {
1152 putchar('\t');vp_print(stdout, vp);putchar('\n');
1158 * Decide what to do with the reply.
1160 switch (fake->reply->code) {
1161 case 0: /* No reply code, must be proxied... */
1162 vp = pairfind(fake->config_items, PW_PROXY_TO_REALM);
1164 eap_tunnel_data_t *tunnel;
1165 DEBUG2(" TTLS: Tunneled authentication will be proxied to %s", vp->vp_strvalue);
1168 * Tell the original request that it's going
1171 pairmove2(&(request->config_items),
1172 &(fake->config_items),
1176 * Seed the proxy packet with the
1179 rad_assert(request->proxy == NULL);
1180 request->proxy = fake->packet;
1181 fake->packet = NULL;
1182 rad_free(&fake->reply);
1186 * Set up the callbacks for the tunnel
1188 tunnel = rad_malloc(sizeof(*tunnel));
1189 memset(tunnel, 0, sizeof(*tunnel));
1191 tunnel->tls_session = tls_session;
1192 tunnel->callback = eapttls_postproxy;
1195 * Associate the callback with the request.
1197 rcode = request_data_add(request,
1199 REQUEST_DATA_EAP_TUNNEL_CALLBACK,
1201 rad_assert(rcode == 0);
1204 * rlm_eap.c has taken care of associating
1205 * the handler with the fake request.
1207 * So we associate the fake request with
1210 rcode = request_data_add(request,
1212 REQUEST_DATA_EAP_MSCHAP_TUNNEL_CALLBACK,
1213 fake, my_request_free);
1214 rad_assert(rcode == 0);
1218 * Didn't authenticate the packet, but
1219 * we're proxying it.
1221 rcode = PW_STATUS_CLIENT;
1224 DEBUG2(" TTLS: No tunneled reply was found for request %d , and the request was not proxied: rejecting the user.",
1226 rcode = PW_AUTHENTICATION_REJECT;
1232 * Returns RLM_MODULE_FOO, and we want to return
1235 rcode = process_reply(handler, tls_session, request,
1238 case RLM_MODULE_REJECT:
1239 rcode = PW_AUTHENTICATION_REJECT;
1242 case RLM_MODULE_HANDLED:
1243 rcode = PW_ACCESS_CHALLENGE;
1247 rcode = PW_AUTHENTICATION_ACK;
1251 rcode = PW_AUTHENTICATION_REJECT;
1257 request_free(&fake);