home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.kerberos
- Path: sparky!uunet!gatech!ee.gatech.edu!asia.eecom.gatech.edu!flur
- From: flur@asia.eecom.gatech.edu (Peter W. Flur)
- Subject: Setting up a slave server under Kerb V4
- Message-ID: <1992Sep16.015100.10859@ee.gatech.edu>
- Sender: news@ee.gatech.edu
- Organization: School of Electrical Engineering, Georgia Institute of Technology
- Date: Wed, 16 Sep 1992 01:51:00 GMT
- Lines: 33
-
- Can someone give me pointers as to what needs to be done in order to do
- the following things:
- 1
- 1) Translate an existing passwor database (straight Unix passwd file) into
- a kerberos principal so that we can put the passwords straight into the
- kdc without having to distribute new passwords.
-
- 2) Set up a slave server. I figured out how to make kprop talk to kpropd,
- but I'm a little confused as to what principals need to be created in
- order for the master server to be able to talk with the slave servers. I
- get kpropd started on the slave, then run kprop on the master, but it
- gives me a "kerberos: unknown principal" message. What principal is
- needed for this?
-
- 3) How does one handle something like the operator account which does
- incremental backups across the network in the middle of the night in
- unattended mode? There is no one to respond to a password prompt.
-
- 4) What is the "standard mode" for installing krb4 with respect to the
- rlogin.ucb, rsh.ucb, etc.? By this, I mean to most people remove the ucb
- versions and require a kerberized session? Do you turn off the rlogind,
- rshd, etc. ports? Do you modify the krb logins not to even run the ucb
- versions upon failure?
-
- Suggestions and/or pointers to more papers would be greatly appreciated.
-
- Peter
-
- --
- -----------------------------------------------------------------------
- Peter Flur, Research Engineer - School of EE, Georgia Tech
- E-MAIL: peter.flur@ee.gatech.edu PHONE: (404) 853-9355
- DUKE UNIVERSITY -- 1991 & 1992 NCAA BASKETBALL CHAMPIONS!!!
-