Upcoming changes to 4.0

[Matthew Newton]

On Fri, Sep 02, 2016 at 09:30:36AM -0400, Alan DeKok wrote:
> People interested in the "latest and greatest" may want to hold
> off for the next month or so.  I will be dropping much of the
> server on the floor, and re-arranging it.

Sounds messy (and nice)!

Slightly related to this, not entirely shelving v3.1.x for the
time being would be good, just to give something that's got more
features than v3.0.x but still works and is pretty stable. (This
may be as easy as not rejecting the odd pull request against it
every now and then for the time being.)

Also means module development for 4.0 has somewhere stable to be
tested in by more than a couple of people.

> So... it's all going away.  Once I've done my re-arrangements, I
> will be re-introducing TCP / TLS functionality, via a better
> (abstracted) system.  The "originate CoA" function is already
> 90% there in the "rlm_radius_client" module,  The detail file

I never managed to look at originate CoA yet - but having a module
to do this that can be called as-and-when rather than being fixed
in the server core sounds much more sensible.

> The end result will be that the server core will know *nothing*
> about RADIUS.  Which has been a goal of mine for 10+ years now.
> :(  The RADIUS knowledge will be limited to a RADIUS transport
> library, a RADIUS server library, and a RADIUS client library.
> All told, probably 4K LoC.  The rest of the server (100K+ LoC)
> will be RADIUS agnostic.

Nice! Project should rename to " Free* ", of course.

> Wish me luck. :)

Sounds like you're going to need it!!

Have fun.

Matthew


-- 
Matthew Newton, Ph.D. <mcn4 at 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 at le.ac.uk>