[2043] in Kerberos-V5-bugs
Re: beta 6 applications don't build
daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Tue Jun 25 10:06:44 1996
Date: Tue, 25 Jun 1996 10:06:31 -0400
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Todd Acheson <acheson@oak.cats.ohiou.edu>
Cc: "Theodore Y. Ts'o" <tytso@MIT.EDU>, krb5-bugs@MIT.EDU
In-Reply-To: Todd Acheson's message of Tue, 25 Jun 1996 08:58:10 -0500,
<SIMEON.9606250810.A@muahost.oak.cats.ohiou.edu >
From: Todd Acheson <acheson@oak.cats.ohiou.edu>
Date: Tue, 25 Jun 1996 08:58:10 -0500
Now for the real meat and potatoes - can your version
V tools interact correctly with my DCE version V
environment?
DCE is based off of an early Alpha distribution of Kerberos. So there
are some krb.conf settings you have to set in order to force our
Kerberos to use some earlier (slightly less secure) cryptographic
algorithms so that you can be compatible with DCE-based Kerberos.
I assume I may have to modify the makefile of the
telnetd to use the DCE kerberos V libraries. Any
thoughts or experience with that process?
DCE does its best to hide Kerberos from users. It doesn't ship the
header files that go with its (ancient) DCE Kerberos V libraries.
Hence, my suggestion is to not even try to use the DCE Kerberos V
libraries.
Use our libraries, and set the configuration files appropriately so that
we can use the old algorithms when talking to your DCE security server.
That's probably the best you can hope for.
I don't know if this satifies what you are trying to do, since you are
being so vague that I still have no idea about what specifically you are
trying to do. In any case, I hope this helps.....
- Ted
k
