[4937] in Kerberos
Re: Kerberos requirements (was Re: SATAN, Dan Farmer, SGI, security, etc.)
daemon@ATHENA.MIT.EDU (Josh Osborne)
Wed Apr 5 13:56:35 1995
From: stripes@uunet.uu.net (Josh Osborne)
To: hughes@logos.ucs.indiana.edu (Larry J. Hughes Jr.)
Date: Wed, 5 Apr 1995 13:33:12 -0400 (EDT)
Cc: kerberos@MIT.EDU
In-Reply-To: <3lueah$s39@usenet.ucs.indiana.edu> from "Larry J. Hughes Jr." at Apr 5, 95 03:51:45 pm
[...if you can't afford to dedicate a new machine to be a kerb. server
try a old Sun3/Vaxstation...]
>Old machines like Sun3s and even Vaxstations can serve up tickets just
>fine, but if you try to set up slave systems and you have a sizeable
>database, forget it. I did this for a while and when our database
>grew past 20,000 users (as it will for many .edu sites) it was taking
>more than 2 hours for the dump-prop-reload hack to happen. It's
>nearly impossible to keep the slaves in sync with the master.
At one of the places I have worked in the past we had a fairly sizeable
database (a few thousand principals), and 3 Kerb. servers. They were
all IBM RT's (about 6 MIPS - roughly twice as fast as a Sun3, slower
then almost any 486). They managed to do Ok. So I immagine for a
largeish database a mid-range 386, or a low-end 486 would do just
fine. Compaired to most any "workstation" class Unix machine, a 486 is
quite cheap, even after you budget the monet to buy a BSDI/OS licence,
or possabble even the time to get one of the free BSD's (or Linux)
running. It should be under $2k.
