I don't see the logic here - RADIUS scales. When you hit that many users
you start using DBM and continue. Saying that it doesn't scale because
you can't get acceptable times with a flat file and a few thousand entries
is ridiculous.
> We have all seen the messages asking how to set up a back-up RADIUS server
>without giving login access (and my suggested plagiarism of Merit's
>Encrypted-Password feature.)
And I've posted ways to make it work.
I've also written a proposal to use some of the functionality built into
the 2.0 engine to add encrypted passwords, grouping, etc to the follow on
release. We're always adding more. As far as simultaneous use restrictions
I have to admit I just don't have the breadth of knowledge needed to
come up with a working, scalable idea. But I don't fell too bad, I haven't
met one person who can do it on their own either. ;-) I'd love to see a
new IETF group formed to work on the problem. If I have the time I'd
participate in it.
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 6920 Koll Center Parkway #220, Pleasanton, CA 94566