RADIUS is a PROTOCOL. Time and time again, I have to explain this
to people. Livingston is credited for getting that protocol into
RFC and breaking the first grounds to creating a radius client
and server.
Now I haven't heard anyone bitching about source to TCP/IP stacks,
FTP servers, and things like this. Just because Livingston opted
to make their source freely available with 1.16 doesn't mean they
are making RADIUS proprietary by not making 2.0 freely available.
Watching everyone bash Livingston for this is really poor on the
user side. They are MANY radius servers out there that
you do NOT get source for. RadiusNT is one of them. We did it
simply for the competetive edge and VALUE ADDED options that
would make someone want to choose RadiusNT over another NT
RADIUS server. If we gave out our source for RadiusNT, then
all the other RADIUS servers for NT would have the same
options, and we would loose our edge. This is plain business
and everyone needs to GET OFF of Livingston's case about it.
They have stated as long as you have a Livingston product
you can have the source . Livingston is still pushing
RADIUS more than any other company, and if you are not
involved in the RFC process, then join the list and
read about whats going on.
-- Dale E. Reed Jr. (daler@iea.com) _____________________________________________________________________ Internet Engineering Associates | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea.com/~daler