[1962] in Kerberos_V5_Development
Re: Configuration directories
daemon@ATHENA.MIT.EDU (Marc Horowitz)
Wed Nov 13 14:46:23 1996
To: source-developers@MIT.EDU, krbdev@MIT.EDU
From: Marc Horowitz <marc@cygnus.com>
Date: 13 Nov 1996 14:45:45 -0500
In-Reply-To: "Richard Basch"'s message of Tue, 12 Nov 1996 23:51:54 -0500
"Richard Basch" <basch@lehman.com> writes:
>> In this case, because we have finally revisited krb5.conf semantics, I
>> agree there should be one common location: /etc/krb5.conf. Vendors who
>> have their own extensions are free to add stanzas to this file, and it
>> won't affect other implementations. If it were not for this
>> flexibility, we probably would have repeated history...
I have one problem with this. I believe (and have flamed about in
person with people who didn't run away :-) that the krb5.conf file
should contain configuration information for the library, which might
include global application defaults. I think it would be terrible for
every application vendor to add a stanza for their own application.
If you think this is wrong, consider automated software installation,
and how difficult it is to programmatically edit shared files (like rc
or services) without stepping on other programs' toes.
If a kerberos vendor adds a feature to their library, then a new
stanza or variable seems fine.
Marc
