[1756] in Kerberos_V5_Development
Re: What isn't installed....
daemon@ATHENA.MIT.EDU (Barry Jaspan)
Tue Sep 10 17:28:55 1996
Date: Tue, 10 Sep 1996 17:28:49 -0400
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: epeisach@MIT.EDU
Cc: krbcore@MIT.EDU
In-Reply-To: <9609102109.AA18544@kangaroo.mit.edu> (message from Ezra Peisach
on Tue, 10 Sep 1996 17:09:03 EDT)
We do not install header files so that a developer can use the
kadm5 library.
We should. There aren't manu.
making install in kadmin/keytab...
/usr/bin/installbsd -c -s kadm5_keytab.local /krb5b1/sbin/kadm5_keytab
/usr/bin/installbsd -c -s kadm5_keytab /krb5b1/sbin/kadm5_keytab
It is not clear that we should be building and installing kadm5_keytab
or kadm5_keytab.local. The functionality of this program is now
contained in kadmin; it did not used to be, which is why the separate
program was written. The argument in favor of kadm5_keytab is that if
you just want to do keytab maintainance, its interafce is slightly
simpler than kadmin's. However, it's another binary to take up space
and confuse users. Furthermore, if the simpler interace is really
needed (which I doubt), kadm5_keytab's usage could be implemented as a
short shell script that calls kadmin.
I guess I'm suggesting that we do not build or install kadm5_keytab.
Maybe we shouldn't even ship the source---if we ship it, we have to
support it, and it is almost an exact duplicate of the code in kadmin.
Barry
