Objections to releasing version 2.2.6?
The zip file can be downloaded from github: https://github.com/FreeRADIUS/freeradius-server/archive/v2.x.x.zip I'm inclined to avoid making a release candidate. There has been very little changed from 2.2.5. About the only change I think could be added is to allow TLS 1.1 and TLS 1.2. Right now they're forbidden. Alan DeKok.
Wouldn't the recent patch to fix the NT_KEY issue be a reasonable reason? The usual link to download 2.2.5 didn't give me a version that fixed the issue here, I had to download the source from git.freeradius.org to get this functionality. Rgds A
On 3 Nov 2014, at 19:25, Alan DeKok <aland@deployingradius.com> wrote:
The zip file can be downloaded from github:
https://github.com/FreeRADIUS/freeradius-server/archive/v2.x.x.zip
I'm inclined to avoid making a release candidate. There has been very little changed from 2.2.5.
About the only change I think could be added is to allow TLS 1.1 and TLS 1.2. Right now they're forbidden.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Alex Sharaz wrote:
Wouldn't the recent patch to fix the NT_KEY issue be a reasonable reason?
That's the locking issue?
The usual link to download 2.2.5 didn't give me a version that fixed the issue here,
Because 2.2.5 doesn't have the fix. New fixes go into a new release.
I had to download the source from git.freeradius.org to get this functionality.
Which is why I included a download link in my previous message. For people to test it... with the fixes. Alan DeKok.
On 3 Nov 2014, at 19:43, Alan DeKok <aland@deployingradius.com> wrote:
Alex Sharaz wrote:
Wouldn't the recent patch to fix the NT_KEY issue be a reasonable reason?
That's the locking issue? Yup
The usual link to download 2.2.5 didn't give me a version that fixed the issue here,
Because 2.2.5 doesn't have the fix. New fixes go into a new release.
I had to download the source from git.freeradius.org to get this functionality.
Which is why I included a download link in my previous message. For people to test it... with the fixes.
Ah sorry, must have missed that, my fault A
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Thanks for adding this to 2.x and 3.x! May I suggest that you remark on these newer protocols being available in the release notes when a feature-supporting version of OpenSSL is used? Nick
About the only change I think could be added is to allow TLS 1.1 and TLS 1.2. Right now they're forbidden.
On 4 Nov 2014, at 09:58, Nick Lowe <nick.lowe@gmail.com> wrote:
Alan DeKok wrote:
Done.
Alan DeKok.
Great - Assume you'll do the same for 3.0.5 before its release?
Shit, no, I spilled orange juice on the release notes, now they're all sticky, I'm sorry I don't think we'll be able add this in as an item... Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS development team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
Done - works well. Thank you, Isaac B. On Wed, Nov 5, 2014 at 10:47 PM, Alan DeKok <aland@deployingradius.com> wrote:
Isaac Boukris wrote:
If I may, I think the fix of UTF-8 username for SQL back end is a nice improvement.
Already done. Please check it.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (5)
-
Alan DeKok -
Alex Sharaz -
Arran Cudbard-Bell -
Isaac Boukris -
Nick Lowe