[2206] in Kerberos
Re: Setting up a slave server under Kerb V4
daemon@ATHENA.MIT.EDU (Shawn Mamros)
Wed Sep 16 15:42:16 1992
Date: 16 Sep 92 17:36:23 GMT
From: mamros@athena.lkg.dec.com (Shawn Mamros)
Reply-To: mamros@athena.lkg.dec.com (Shawn Mamros)
To: kerberos@shelby.Stanford.EDU
flur@asia.eecom.gatech.edu (Peter W. Flur) asks how does one...
|> 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?
The master server needs to have a key for rcmd.kerberos@<REALM> in /etc/srvtab.
The slaves need rcmd.<hostname>@<REALM> in /etc/srvtab.
Be warned: If you plan on having an rcmd.<hostname>@<REALM> key on your master
server as well, make sure you place that key BEFORE the one for rcmd.kerberos
(unless, of course, your master server's hostname is "kerberos", in which
case you only need the one...) in the keyfile. Some of the other programs
use krb_rd_req() with a principal name of "rcmd" and an instance of "*", which
will use rcmd.kerberos if it comes first (usually not what you want).
Oh yeah, if you happen to be using the version of Kerberos supplied with
ULTRIX V4.x, be warned that kprop and kpropd there use the principal name
"kprop.<hostname>@<REALM>" on both master and slaves, instead of rcmd.
(No, it wasn't my idea, so don't shoot me...)
-Shawn Mamros
E-mail to: mamros@athena.lkg.dec.com
