Re: Unix passwd hash

Dave Andersen (angio@aros.net)
Sat, 22 Jun 1996 11:01:58 -0600 (MDT)

No.. RADIUS gets bogged down when using a large users file, because it
parses the entire file (in the case of Livingston) each time it
authenticates someone.

The speed of using the "UNIX" type authentication depends on the speed of
the getpwnam() call (or getspwnam()) in your operating system. If your
OS uses flat file access for it (such as Linux), then yes, you'll see
some degredation. If it uses a database (FreeBSD, BSDI, SunOS, Solaris)
then the peformance stays in the good range. My passwd file has around
1700 entries in it and authentication (under FreeBSD) is very quick.

The hashing refers to putting the users file itself in to a database.
You have to remake the database whenever you change the users file. This
should be documented in the radius notes, and if not, MZ and others have
posted the directions about how to accomplish it before.

-Dave Andersen

Lo and behold, Paul Castro once said:
> Hi All,
>
> I have seen a mention of Radius getting bogged down when using the
> the *nix passwd table after 1,000+ users are in it,
> and that a solution was to have it
> compiled into some kind of hash table with the dbm library..
>
> I cannot for the life of me find FAQs etc, for this though I do see
> it mentioned in the Radius source. I can't seem to find this info in my
> old digests either anymore..
>
> For example, what keeps the hash table up to date etc.? Puhleez help- !
>
> TIA
>
> [* Rockland Gate Systems *]
>
>

-- 
angio@aros.net                Complete virtual hosting and business-oriented
system administration         Internet services.  (WWW, FTP, email)
http://www.aros.net/          http://www.aros.net/about/virtual
  "There are only two industries that refer to their customers as 'users'."