[1815] in Kerberos_V5_Development
kadm5 remote server testing quasi-functional
daemon@ATHENA.MIT.EDU (Barry Jaspan)
Fri Sep 27 17:29:01 1996
Date: Fri, 27 Sep 1996 17:27:41 -0400
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: krbdev@MIT.EDU
In the "random cool things department," the kadm5 tests can now be run
with a remote server host with little extra effort. If you specify
the macros TEST_SERVER and TEST_PATH on the make command line, as in
ddn% make check TEST_SERVER=beeblebrox TEST_PATH=/marc/krb5/build/kadmin
then the test system will set up the host beeblebrox as the KDC
(instead of localhost) and set up the local host's krb5.conf to point
to it (instead of localhost). The TEST_PATH macro points to the top
of the kadmin tree on the remote host. That's all there is to it, but
expect this code to be fragile for a while.
Note: This requires that "rsh $TEST_SERVER" work. At OV, we used
/usr/ucb/rsh and just created /.rhosts files on our test machines,
because it was too much of a pain to use a krb5 rshd to control access
to krb5 tests. However, since rsh and rshd at Athena are V4 and the
kadm5 test system is no longer frobbing /etc/krb.*, /etc/v5srvtab,
/etc/passwd, ..., it isn't a hassle. So you just need an identically
named account on $TEST_SERVER that you have permission to krsh to. We
can make this work with a krb5 rsh without too much effort in the
future.
At the moment, you also need to have /mit/gnu attached, because it
uses an explicit path for expect. Obviously this will need to be
fixed, too.
This is not necessarily something that we need to run all the time,
but it is useful for checking for byteorder correctness, etc; it was
particularly useful at OV for when we were running rlogin etc. tests
because it enabled us to test inter-OS compatibility quickly.
Barry
