Maintaining a (very) dynamic user list with freeradius

[Bjørn Mork]

Jos Vos <jos at xos.nl> writes:

> Deviating from the standard RHEL packages and maintaining your own RPM
> (this is for a large number of systems) is probably doable (often you
> encounter incompatibiities with older compilers and libraries, but
> freeradius is a relatively isolated piece of software, I think), but it
> also means I have to take care of security problems etc. myself, while
> RH does that for me now.  That's why I only tend to maintain my own
> version if really necessary.

This is most likely a case where, although not strictly necessary, an
upgrade will save you lots of work and frustrations.

But if RH and you still feel FreeRadius 1.0.1 is the way to go, then I
assume that RH provides the proper documentation and support for this
out-dated version.

But you are of course right: Using RHEL4 compilers and libraries is
probably going to cause a number of problems too.   Or to be more
precise:  Using RHEL4 is probably going to cause a number of problems. 

I would strongly suggest to read this bug report and try to understand
the implications: https://bugzilla.redhat.com/show_bug.cgi?id=166873

Short summary for the impatient: RHEL4 includes a random CVS snapshot of
mod_perl2, which is neither compatible with mod_perl1 nor mod_perl2,
since there were major API changes between this CVS snapshot and the
mod_perl2 release.  This makes it completely unusable in the real world.
This is not considered a bug.

You can expect the FreeRadius version in RHEL4 to be in the same state:
A random snapshot taken at the time of RHEL4 release, and not really
something the developers of FreeRadius would recommend using.  Not now,
anyway.  Which you've probably learned now


Bjørn