[8090] in Kerberos
Re: Bug fix: kdc.conf not being read
daemon@ATHENA.MIT.EDU (Christopher Seawood)
Sun Sep 22 16:59:21 1996
Date: Sun, 22 Sep 1996 13:47:06 -0700 (PDT)
From: Christopher Seawood <cseawood@qualcomm.com>
Reply-To: Christopher Seawood <cseawood@qualcomm.com>
To: Sam Hartman <hartmans@MIT.EDU>
Cc: kerberos@MIT.EDU
In-Reply-To: <tslbuezm22r.fsf@tertius.mit.edu>
On 22 Sep 1996, Sam Hartman wrote:
>
> First, when sending patches as mime attachments, please do not
> base64 encode them; it is annoying and unnecessary. If your mailer
> cannot be configured to include attachments in 7bit encoding, then
> please include the patch in the body of the message instead of in a
> separate MIME part.
>
First, I included a disclaimer saying that I was attaching the patch via
pine plus a URL to the patch. I thought the patch was a bit big to pipe to
everybody. Second, as far as the annoyance of base64 encode, that's a
personal preference related to your mail reader. I did not set up pine to
purposefully send base64, I just sent an attachment (which, btw, I
normally don't do).
> Second, I think you are confused about the location of
> kdc.conf. The kdc.conf file must live in either the
> $prefix/lib/krb5kdc or the file specified in the KRB5_KDC_PROFILE
> environment variable. For various reasons mostly dealing with bad
> design choices in certain database abstractions, you cannot allow
> krb5.conf to specify the location of kdc.conf, as kdc.conf may specify
> an alternate location for krb5.conf. If you find a documentation
> reference that indicates this is not the case, we will certainly fix
> either the code or the docs.
>
Section 4.1.1.1 of install.ps states:
"The krb5.conf file may contain a pointer to kdc.conf, which you need to
change if you want to move kdc.conf to another location. "
Appendix A1 of this same file shows an example of a krb5.conf file with
the following statement:
"
For the KDCs, add a section onto the end of the krb5.conf file telling
where the kdc.conf file is located, as in the following example:
[kdc]
profile = /usr/krb5/lib/krb5kdc/kdc.conf
[logging]
kdc = FILE:/dev/tty9
admin_server = FILE:/dev/tty9
default = FILE:/dev/tty9
"
And Appendix A2 has an example of a kdc.conf file. /etc/krb5.conf
referencing kdc.conf seems more appropriate than kdc.conf referencing
/etc/krb5.conf.
Does the profile field of a realm in kdc.conf actually get used? I do not
recall running across any code that depends upon. I'm going to take it out
and see what happens. Yippie! More testing. Glad I got my rollerblading in
this morning. :)
-----
Chris Seawood <cseawood@qualcomm.com> - Software Engineer / Unix Sysadmin
http://www.qualcomm.com/~cseawood/ - Prince Fanatic / Linux Advocate
Opinions stated are NOT an (un)official representation of QUALCOMM Incorporated
