| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
To: kerberos@MIT.EDU Date: 21 Feb 1995 14:14:43 GMT From: orion@iastate.edu (Phi H Truong) Reply-To: orion@iastate.edu (PUT YOUR NAME HERE) In article <EDHILL.95Feb20125601@strobe.weeg.uiowa.edu>, Ed Hill <edhill@strobe.weeg.uiowa.edu> wrote: > >We are setting up a cluster of machines(AIX boxes), and are trying to figure >out the best way to distribute /etc/passwd information across the nodes. We >don't want to use NIS because we want to keep shadow password functionality, so >the next step is to look towards kerberos, DCE, etc... > >However, kerberos does not seem to provide the ability to keep a central >registry of /etc/passwd type information, it just provides the name and passwd >(and of course the protocols for authentication, etc...). DCE provides the >registry with account type information, but we are not quite ready to make the >jump to DCE yet. > >How do other places keep /etc/passwd information (uids, home dirs, shells) in >sync across multiple machines that you are running kerberos on. > Use Bind/Hesiod for informations such as homedir, shells, uid, grpid, grplist,... etc. Use kerberos for authentication. At our site, our /etc/passwd doesn't have anything. -- _____ Phi H. Truong "Hmmmmmmmm....... " orion@iastate.edu ISU Computation Center Systems Analyst 237 Durham Center ph: (515) 294 -1420
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |