Segmentaton fault in 3.0.5
Hi list, Since 3.0.5 ( FreeRADIUS Version 3.0.5 (git #8bc2d13), for host i486-pc-linux-gnu,) Program received signal SIGSEGV, Segmentation fault. 0xb7a45287 in eappeap_process () from /usr/lib/freeradius/rlm_eap_peap.so (gdb) bt #0 0xb7a45287 in eappeap_process () from /usr/lib/freeradius/rlm_eap_peap.so #1 0xb7a433f9 in ?? () from /usr/lib/freeradius/rlm_eap_peap.so #2 0xb7a57ea6 in ?? () from /usr/lib/freeradius/rlm_eap.so #3 0xb7a58268 in eap_method_select () from /usr/lib/freeradius/rlm_eap.so #4 0xb7a57100 in ?? () from /usr/lib/freeradius/rlm_eap.so #5 0x0806af04 in ?? () #6 0x0806a2c0 in ?? () #7 0x0806a534 in ?? () #8 0x0806b55a in modcall () #9 0x08066467 in indexed_modcall () #10 0x080672eb in process_authenticate () #11 0x08055d3d in rad_authenticate () #12 0x08079eb7 in ?? () #13 0x0807597d in ?? () #14 0x08077d87 in request_receive () #15 0x08060bfd in ?? () #16 0x080743af in ?? () #17 0xb7fa6799 in fr_event_loop () from /usr/lib/freeradius/libfreeradius-radius.so #18 0x0807add3 in radius_event_process () #19 0x08054859 in main () Nicolas CLO
On 24-11-14 10:18, nicolas.clo@ricoh-industrie.fr wrote:
Hi list,
Since 3.0.5
( FreeRADIUS Version 3.0.5 (git #8bc2d13), for host i486-pc-linux-gnu,)
Program received signal SIGSEGV, Segmentation fault. 0xb7a45287 in eappeap_process () from /usr/lib/freeradius/rlm_eap_peap.so
Probably the issue mentioned in https://github.com/FreeRADIUS/freeradius-server/issues/839. I've got a patch described in the last edit (Changing fake->packet->offset to request->proxy->offset as peap.c:1141). Another option might be to turn the option proxy_tunneled_request_as_eap on (given that the backend you're using supports it). -- Herwin Weststrate
Same problem when turn on proxy_tunneled_request_as_eap (7) Found Auth-Type = EAP (7) # Executing group from file /etc/freeradius/sites-enabled/inner-tunnel (7) authenticate { (7) eap: Expiring EAP session with state 0x83292e1e832034ff (7) eap: Finished EAP session with state 0x83292e1e832034ff (7) eap: Previous EAP request found for state 0x83292e1e832034ff, released from the list (7) eap: Peer sent method MSCHAPv2 (26) (7) eap: EAP MSCHAPv2 (26) (7) eap: Calling eap_mschapv2 to process EAP data (7) eap_mschapv2: cancelling authentication and letting it be proxied (7) eap: No EAP proxy set. Not composing EAP (7) [eap] = handled (7) } # authenticate = handled (7) } # server inner-tunnel (7) Virtual server sending reply (7) eap_peap: Got tunneled reply code 0 (7) eap_peap: Tunnelled authentication will be proxied to LOCAL De : Herwin Weststrate <herwin@quarantainenet.nl> A : FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Date : 24/11/2014 10:55 Objet : Re: Segmentaton fault in 3.0.5 Envoyé par : freeradius-users-bounces+nicolas.clo=ricoh-industrie.fr@lists.freeradius.org On 24-11-14 10:18, nicolas.clo@ricoh-industrie.fr wrote:
Hi list,
Since 3.0.5
( FreeRADIUS Version 3.0.5 (git #8bc2d13), for host i486-pc-linux-gnu,)
Program received signal SIGSEGV, Segmentation fault. 0xb7a45287 in eappeap_process () from /usr/lib/freeradius/rlm_eap_peap.so
Probably the issue mentioned in https://github.com/FreeRADIUS/freeradius-server/issues/839. I've got a patch described in the last edit (Changing fake->packet->offset to request->proxy->offset as peap.c:1141). Another option might be to turn the option proxy_tunneled_request_as_eap on (given that the backend you're using supports it). -- Herwin Weststrate - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 24-11-14 11:02, nicolas.clo@ricoh-industrie.fr wrote:
Same problem when turn on proxy_tunneled_request_as_eap
Sorry, my bad. It would have fixed the original problem from the bug report I linked though. Then I guess the only fix is to apply the change I mentioned. -- Herwin Weststrate
Herwin Weststrate wrote:
Probably the issue mentioned in https://github.com/FreeRADIUS/freeradius-server/issues/839. I've got a patch described in the last edit (Changing fake->packet->offset to request->proxy->offset as peap.c:1141). Another option might be to turn the option proxy_tunneled_request_as_eap on (given that the backend you're using supports it).
I've pushed a fix. Alan DeKok.
participants (3)
-
Alan DeKok -
Herwin Weststrate -
nicolas.clo＠ricoh-industrie.fr