freeradius 2.2.1 release date?
Is 2.2.1 close to release, or is no release planned because 3.0 is so close? We are using 2.2.0 and a few of the features introduced in 2.2.1 would be really useful for us. In particular expansion of the "reference" configuration item to adjust the accounting SQL queries. -- Bruce Bruce Bauman - Systems Administrator Rutgers University Office of Information Technology Campus Computing Services - Central Systems and Services Office ~ (848) 445-6363
On 27 Jun 2013, at 17:59, Bruce Bauman <bbauman@oit.rutgers.edu> wrote:
Is 2.2.1 close to release, or is no release planned because 3.0 is so close?
We are using 2.2.0 and a few of the features introduced in 2.2.1 would be really useful for us. In particular expansion of the "reference" configuration item to adjust the accounting SQL queries.
That's not available in 2.2.1, and it won't be backported. Query by reference/failover between arbitrary numbers of queries is only in 3.0.0. 2.2.1 should be released within the next couple of weeks, 3.0.0 should be released very soon. If you're actively working on your FreeRADIUS configuration you should upgrade to 3.0.0, 2.x.x will mainly be bug fixes from now on. Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team
Two questions. Will there be a 2.2.2 tarball soon? Will 2.2.2 include the check_cert_issuer fix, or will that fix come later? Thanks. -- Bruce Bruce Bauman - Systems Administrator Rutgers University Office of Information Technology Campus Computing Services - Central Systems and Services Office ~ (848) 445-6363
On 23 Sep 2013, at 19:29, Bruce Bauman <bbauman@oit.rutgers.edu> wrote:
Two questions.
Will there be a 2.2.2 tarball soon?
Yes, and it'll be released considerably sooner if people post more specific feedback about issues they're experiencing.
Will 2.2.2 include the check_cert_issuer fix, or will that fix come later?
It'll include the fix. -Arran Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team
We want to modify our FreeRadius (2.2.x) configuration such that the username is always converted to all lower case, both for authentication and accounting. In policy.conf we defined: rewrite_username_lowercase { update request { User-Name := "%{tolower:%{User-Name}}" } } And then at the beginning of the accounting and authorize sections we "call" rewrite_username_lowercase. This seems to work: JohnSmith -> johnsmith in both our authorization and accounting. Is there a better place to do this such that it's only done in one place and affects the username globally? Thanks. -- Bruce
Bruce Bauman wrote:
Is there a better place to do this such that it's only done in one place and affects the username globally?
Put it in "authorize" and "preacct". There is no "global" place to change the name. There is authorize, which can re-write Access-Requests, and preacct, which can rewrite Accounting-Requests. And there is NO connection between the two kinds of packets. FreeRADIUS doesn't track that. The NAS does. Alan DeKok.
participants (4)
-
Alan DeKok -
Arran Cudbard-Bell -
Bruce Bauman -
Phil Mayers