Centralized DB of "system" users

[Da Rock]

On Sun, 2008-12-14 at 17:59 +0700, Outback Dingo wrote:
> > Wouldn't kerberos be a better alternative? One server (maybe a
> > replicated backup), and all services authenticate with that. Saves
> > shadow on the wire...
> >
> 
> I think the ulitimate question is going to be at what level of pain does the
> person wish to suffer to achieve his goals
> there are numerous ways to do it, though some can be painful, if not
> experienced. I struggle to get my brain around
> an environment with mulitple OSes in it, where i would lean towards the LDAP
> method, though you raise a valid point
> where kerberos could fit nicely, though Im not sure we are aware of the long
> term goals or the project where one might
> be adding in other types of Operating Systems. Then we have the discussion
> of interoperability. If it stays as in his game
> plan and  doesnt encounter scope creep (not like it doesnt happen) at some
> time, he might wish to choose the best overall
> design to implement, again my vote would be LDAP. it is the most globally
> scaable, relocable and interoperable once its
> deployed allowing for future growth without a serious amount of pain.

Actually kerberos is quite widely supported in one form or other and is
mostly interoperable (from my understanding anyway), and its
surprisingly easy to implement- easier than ldap in my opinion. Even M$
crap uses it (different implementation, but basically the same).

Plus the security it offers is by far worth the pain that could be
caused. You mainly have to concentrate attention on the kdc access, as
all auth runs off it, instead of every service on the network.