Freeradius v3.0.11 crashes after sql group lookup
Hello, I'm testing FR3.0.11 (on Debian Jessie) as an upgrade to our FR3.0.5 (running on Debian Wheezy). Tests runned fine until I test it with an unknown account : - Auth is EAP/PEAP + MSCHAPv2 - Accounts are stored in sql backend (MySQL) for this SSID. FR crashes with SIGSEGV after : sql_groupcmp finished: User is NOT a member of group wifi-public I've attached freeradius -X output through gdb. Regards. -- Philippe MARASSE Responsable pôle Infrastructures - DSIO Centre Hospitalier Henri Laborit CS 10587 - 370 avenue Jacques Cœur 86021 Poitiers Cedex Tel : 05.49.44.57.19
On Jun 22, 2016, at 6:23 AM, Philippe MARASSE <philippe.marasse@ch-poitiers.fr> wrote:
I'm testing FR3.0.11 (on Debian Jessie) as an upgrade to our FR3.0.5 (running on Debian Wheezy). Tests runned fine until I test it with an unknown account : - Auth is EAP/PEAP + MSCHAPv2 - Accounts are stored in sql backend (MySQL) for this SSID.
FR crashes with SIGSEGV after : sql_groupcmp finished: User is NOT a member of group wifi-public
Fixed already in v3.0.x. Alan DeKok.
Hello, Thanks for your answer, so which version should I use, especially for my futures upgrades ? latest tagged or latest HEAD of 3.0.x branch ? Regards. Le 22/06/2016 à 15:04, Alan DeKok a écrit :
On Jun 22, 2016, at 6:23 AM, Philippe MARASSE <philippe.marasse@ch-poitiers.fr> wrote:
I'm testing FR3.0.11 (on Debian Jessie) as an upgrade to our FR3.0.5 (running on Debian Wheezy). Tests runned fine until I test it with an unknown account : - Auth is EAP/PEAP + MSCHAPv2 - Accounts are stored in sql backend (MySQL) for this SSID.
FR crashes with SIGSEGV after : sql_groupcmp finished: User is NOT a member of group wifi-public Fixed already in v3.0.x.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Philippe MARASSE Responsable pôle Infrastructures - DSIO Centre Hospitalier Henri Laborit CS 10587 - 370 avenue Jacques Cœur 86021 Poitiers Cedex Tel : 05.49.44.57.19
On Wed, Jun 22, 2016 at 03:29:05PM +0200, Philippe MARASSE wrote:
Thanks for your answer, so which version should I use, especially for my futures upgrades ? latest tagged or latest HEAD of 3.0.x branch ?
v3.0.x HEAD if it fixes your problem. It will become 3.0.12 at some point anyway. Matthew -- Matthew Newton, Ph.D. <mcn4@leicester.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
Thanks, My first test with 3.0.x HEAD seems to work. I feel somewhat unlucky with my FR upgrades, each time I take a release, I run into a bug :-). Regards. Le 22/06/2016 à 15:44, Matthew Newton a écrit :
On Wed, Jun 22, 2016 at 03:29:05PM +0200, Philippe MARASSE wrote:
Thanks for your answer, so which version should I use, especially for my futures upgrades ? latest tagged or latest HEAD of 3.0.x branch ? v3.0.x HEAD if it fixes your problem. It will become 3.0.12 at some point anyway.
Matthew
-- Philippe MARASSE Responsable pôle Infrastructures - DSIO Centre Hospitalier Henri Laborit CS 10587 - 370 avenue Jacques Cœur 86021 Poitiers Cedex Tel : 05.49.44.57.19
On Jun 22, 2016, at 12:03 PM, Philippe MARASSE <philippe.marasse@ch-poitiers.fr> wrote:
My first test with 3.0.x HEAD seems to work. I feel somewhat unlucky with my FR upgrades, each time I take a release, I run into a bug :-).
We try, but we're not perfect. The good news is that the changes that will be in 3.0.12 are very minor. The 3.0 release is stable, and not changing. Even the 3.1 (soon to be 3.2) release is feature frozen now. So there will be bug fixes, but no more changes. All of the new work is going into the v4 branch. The good news is that there will be many more features and benefits. The bad news is that we'll have to change some of the configuration in incompatible ways. Alan DeKok.
participants (3)
-
Alan DeKok -
Matthew Newton -
Philippe MARASSE