We're trying coordinate our release schedule for our next version of RHEL (RHEL 6.0). As it stands now RHEL6 will release with FreeRADIUS version 2.1.7. But it takes us a very long time to prepare a new RHEL release and in the interim there may be an opportunity to upgrade the version of FreeRADIUS in RHEL6 to something newer should you decide to make a new release in the next few months. I seem to recall a discussion that the next significant release will be 2.2.0. Is that still correct? Do you have an anticipated release date for that? What major new features and/or bug fixes do you anticipate being in it? I ask these questions because I might be able to ask management to anticipate we will need to rebase the version of FreeRADIUS to something newer in RHEL6 than the current 2.1.7. But to do so I have to provide dates and the supporting reasons why this would be a good thing to do. Thanks. -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
John Dennis wrote:
We're trying coordinate our release schedule for our next version of RHEL (RHEL 6.0). As it stands now RHEL6 will release with FreeRADIUS version 2.1.7. But it takes us a very long time to prepare a new RHEL release and in the interim there may be an opportunity to upgrade the version of FreeRADIUS in RHEL6 to something newer should you decide to make a new release in the next few months.
I plan on releasing 2.1.8 soon. It will be 2.1.7, plus a number of bug fixes, but *without* any new features.
I seem to recall a discussion that the next significant release will be 2.2.0. Is that still correct? Do you have an anticipated release date for that? What major new features and/or bug fixes do you anticipate being in it?
The TCP work will go into 2.2.0. I'm also waiting for some other changes for 2.2.0, which require changing the internal API quite a bit. The bad news is that old modules won't work any more. The good news is that the server will be able to handle VENDOR codes over 32K. Since IANA is already handling out codes over 32K, this change is needed for any "long term support" version of the server. I would prefer to release 2.2.0 in January.
I ask these questions because I might be able to ask management to anticipate we will need to rebase the version of FreeRADIUS to something newer in RHEL6 than the current 2.1.7. But to do so I have to provide dates and the supporting reasons why this would be a good thing to do.
I would say 2.1.8 this week. I'll put up a proposed release shortly. Alan DeKok.
I plan on releasing 2.1.8 soon. It will be 2.1.7, plus a number of bug fixes, but *without* any new features.
Previously, you had mentioned you were going to start looking at including bug 17 (MS-CHAP incorrectly calculating challenge due to case mismatch of userid) in 2.1.8. I realize other things have come up since then and that plans can change. So, is it still on the roadmap for 2.1.8? (Please don't take this as me pushing, I'm just curious about your plans..) Thank you again Alan for all of the time and energy you put into making FreeRadius the best! Neal
Garber, Neal wrote:
Previously, you had mentioned you were going to start looking at including bug 17 (MS-CHAP incorrectly calculating challenge due to case mismatch of userid) in 2.1.8. I realize other things have come up since then and that plans can change. So, is it still on the roadmap for 2.1.8? (Please don't take this as me pushing, I'm just curious about your plans..)
Oh, push all you want. My main worry is that MS-CHAP is pretty core to the system, and *any* changes make me paranoid. I think you had at least one other person test it. If you could get a few more people to give feedback, I'd be more confident that it doesn't destroy anything.
Thank you again Alan for all of the time and energy you put into making FreeRadius the best!
What can I say, I'm motivated. :) Alan DeKok.
My main worry is that MS-CHAP is pretty core to the system, and *any* changes make me paranoid.
I understand and I totally agree with you.
I think you had at least one other person test it.
Yes, one person who was having the problem described by bug 17 contacted me off-list. I told him to get the patch from bugzilla. He applied it and confirmed that the patch correct the issue for him (and didn't cause any other issues). Also, we've been running with it on 3 servers for more than 3 months now with no problems.
If you could get a few more people to give feedback, I'd be more confident that it doesn't destroy anything.
Ok. I'll start begging again ;-). I think Arran and Alan B. mentioned a while ago that they might be willing to test it. Arran/Alan B: Have either of you had a chance to do any testing? If a few sites that use MS-CHAP auth. can apply the patch and verify that it doesn't break anything, it would be greatly appreciated. Others have reported similar issues in the past and this patch *may* resolve some of these issues: http://lists.freeradius.org/mailman/htdig/freeradius-users/2009-August/msg00... http://lists.freeradius.org/mailman/htdig/freeradius-users/2009-August/msg00... http://lists.freeradius.org/mailman/htdig/freeradius-users/2009-August/msg00... http://lists.freeradius.org/mailman/htdig/freeradius-users/2009-March/msg002... http://lists.freeradius.org/mailman/htdig/freeradius-users/2008-December/msg... http://lists.freeradius.org/mailman/htdig/freeradius-users/2008-June/msg0023... http://lists.freeradius.org/mailman/htdig/freeradius-users/2008-May/msg00015... http://lists.freeradius.org/mailman/htdig/freeradius-users/2008-May/msg00595... http://lists.freeradius.org/mailman/htdig/freeradius-users/2008-February/msg... http://lists.freeradius.org/mailman/htdig/freeradius-users/2007-August/msg00... http://lists.freeradius.org/mailman/htdig/freeradius-users/2007-April/msg000... http://lists.freeradius.org/mailman/htdig/freeradius-users/2007-February/msg... http://lists.freeradius.org/mailman/htdig/freeradius-users/2006-December/msg... http://lists.freeradius.org/mailman/htdig/freeradius-users/2006-November/msg...
Ok. I'll start begging again ;-). I think Arran and Alan B. mentioned a while ago that they might be willing to test it.
Arran/Alan B: Have either of you had a chance to do any testing?
Sorry, transatlantic issues got in the way. Could you repost the patches to me off list and I promise i'll have a look at them tomorrow. -Arran
Could you repost the patches to me off list and I promise i'll have a look at them tomorrow.
Done - thank you for your time and (continued) willingness to help Arran. Yesterday, I sent E-mail to 5 other users that previously reported a problem that *might* be fixed by the bug 17 patch. Here's a summary of the responses I've received so far: 1. Still having the problem and is interested in the patch 2. Since they didn't have a solution, they abandoned FreeRadius :-( 3. Interested in testing the patch 4. Still having the problem and is interested in testing 5. No response yet I'll keep you posted as I get more info.
Thank you Alan -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
participants (4)
-
Alan DeKok -
Arran Cudbard-Bell -
Garber, Neal -
John Dennis