Bug 827858
Summary: | Segfault during EAP | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Thomas Jansen <mithi> | ||||
Component: | freeradius | Assignee: | John Dennis <jdennis> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 17 | CC: | jdennis, lemenkov, lukasz | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-08-14 21:57:21 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Thomas Jansen
2012-06-03 10:29:23 UTC
Thank you for your bug report. Since you say this is reproducible I'd appreciate if you could provide the reproducer and/or the *full* debug output of radiusd when running the reproducer. To get debug output do this as root: stop the existing daemon via systemctl stop radiusd.service Then run the server in debug mode: /sbin/radiusd -X The reproducer is important because many people run EAP successfully so there must be something specific to your installation. Created attachment 588899 [details]
Output of radiusd -X
The attachment above contains the debug output, where I replaced my passwords with XXX. What exactly is meant by 'reproducer'? Perhaps I'll just give you a general picture of what I'm trying to do (and successfully did until I upgraded to F17). I use radiusd on a virtual machine for authentication in my WiFi network. It uses an LDAP backend that stores usernames and passwords. If I try to connect my phone or my laptop to the WiFi network, either device fails to establish a connection and radiusd segfaults. Reproducable in this context means that every time I try to connect either device to the network radiusd segfaults. I did not change my config during the upgrade from F16 to F17 and /etc/raddb does not contain any *.rpmnew files. I'm by no means a freeradius expert, so it might be config-related. The same config however used to work fine under the latest freeradius in F16 though. Manual downgrading to freeradius-2.1.12-3.fc16.x86_64 and freeradius-ldap-2.1.12-3.fc16.x86_64 on a F17 system is a viable workaround. This version does not segfault. Hi We have the same problem, after upgrade to FC17 after a few minutes we got: Jul 10 13:02:25 see-you-later kernel: [ 1765.775309] radiusd[1070]: segfault at c0 ip b70ed6f2 sp b589f1b0 error 4 in libfreeradius-eap-2.1.12.so[b70e8000+9000] Jul 10 13:36:37 see-you-later kernel: [ 3818.239572] radiusd[2230]: segfault at c0 ip b70026f2 sp b57b41b0 error 4 in libfreeradius-eap-2.1.12.so[b6ffd000+9000] Jul 10 13:36:59 see-you-later kernel: [ 3839.694793] radiusd[2253]: segfault at c0 ip b706d6f2 sp b68211b0 error 4 in libfreeradius-eap-2.1.12.so[b7068000+9000] Jul 10 14:00:10 see-you-later kernel: [ 5230.510892] radiusd[2281]: segfault at c0 ip b705d6f2 sp b580f1b0 error 4 in libfreeradius-eap-2.1.12.so[b7058000+9000] [root@see-you-later log]# rpm -q freeradius freeradius-2.1.12-5.fc17.i686 Alan DeKok (FreeRADIUS author) responded on the freeradius-users list with this comment in reference to this bug. I will do a rebuild and push. This is typically caused by having discordant versions of OpenSSL installed. i.e. the server was built using version X, and the current OpenSSL library is version Y. There's really no solution, other than to re-build && re-link the server. I can put some hacks in, but all they'll do is ensure that the server doesn't crash. It WON'T cause authentication to work. freeradius-2.1.12-6.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/freeradius-2.1.12-6.fc17 freeradius-2.1.12-6.fc17 has been submitted to updates-testing, it may take a day before it appears in the repos. Please test this and see if it resolves your problems. If not please let me know the version of openssl you're running. This fixes the problem for me. The following versions were used in the quick test I just did:
> rpm -q openssl freeradius
openssl-1.0.0j-2.fc17.x86_64
freeradius-2.1.12-6.fc17.x86_64
Thanks for your effort.
Thank you for testing Thomas. Since this worked for you would you please click on this link and give it a positive karma vote, that will speed it's inclusion into the stable repos. https://admin.fedoraproject.org/updates/freeradius-2.1.12-6.fc17?_csrf_token=dad239723f63730a64a20b6fc5d2a52d33a3df8b For me freeradius-2.1.12-6.fc17.i686 also works without any problems and stable. Thank You. Package freeradius-2.1.12-6.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing freeradius-2.1.12-6.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-11708/freeradius-2.1.12-6.fc17 then log in and leave karma (feedback). freeradius-2.1.12-6.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |