[1969] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: krb5-libs/182: /etc/v5srvtab -> /etc/krb5.keytab

daemon@ATHENA.MIT.EDU (Barry Jaspan)
Thu Nov 14 10:55:43 1996

Date: Thu, 14 Nov 1996 10:55:16 -0500
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: tlyu@MIT.EDU
Cc: krbdev@MIT.EDU, krb5-bugs@MIT.EDU
In-Reply-To: <9611140719.AA09550@tesla-coil.MIT.EDU> (message from Tom Yu on
	Thu, 14 Nov 1996 02:19:25 -0500)


   Global variable removal has been backed out, pending post-1.0 design
   work.  Unix keytab name defaults to /etc/krb5.keytab; DOS keytab name
   defaults to krb5kt (to match krb5cc).  Still needs to be documented
   though.  I guess I can do that as well.

Yes, it definately needs to be documented, or there are going to be 75
messages on the Kerberos list asking "why is 1.0 reporting 'keytab not
found'?".

In install.texinfo, there is a node Installing Kerberos V5->Installing
KDCs->Upgrading existing Master and Slave KDCs to the current
release.  Probably what you should do is add an Upgrading node to the
top level menu so it looks like

>> * Menu:
>> 
>> * Introduction::
>> * Realm Configuration Decisions::
>> * Building Kerberos V5::
>> * Installing Kerberos V5::
>> * Upgrading existing Kerberos V5 installations::   
>> * Bug Reports for Kerberos V5::
>> * Files::

Under that top-level menu entry, put the upgrading KDCs node I already
wrote, and add another section on the keytab name change.

Also make sure the keytab name relation is documented in the krb5.conf
man page, the new default value is documented, and mention that the
old default changed and how to fix it.

Barry

home help back first fref pref prev next nref lref last post