[359] in Kerberos-V5-bugs
Re: Building Kerberos V on HP-UX: Krb4KDCCompat
daemon@ATHENA.MIT.EDU (Hugh C. Lauer)
Thu Sep 23 17:29:27 1993
To: tytso@MIT.EDU (Theodore Ts'o)
Cc: "Hugh C. Lauer" <lauer@merl.com>, krb5-bugs@MIT.EDU
In-Reply-To: Your message of "Tue, 21 Sep 93 20:04:22 EDT."
Date: Thu, 23 Sep 93 15:38:19 -0400
From: "Hugh C. Lauer" <lauer@merl.com>
> The take home message from all of this is that the V4 compatibility in
> the KDC isn't enough, all by itself.
So if we have never had Kerberos installed, then we don't need the V4
compatibility, even if some clients are still using V4? Is that correct?
>
> If you still want Kerberos V4, then you'll need to grab the Kerberos V4
> package, and compile that in a separate tree. Then configure site.def
> to use the V4 library which you've compiled from that tree.
>
> I ran across a second use of -lkrb, namely in building admin/convert. This
> doesn't seem to go away even when I commented out Krb4KDCCompat. Are there
> any other uses of -lkrb anywhere? If so, where do I get it (short of having
> to go back and port Kerberos IV to HP-UX)?
>
> Yeah; that's a bug; admin/convert shouldn't be built if Krb4KDCCompat is
> commented out. (Actually, in the next release, we actually use a
> separate variable to control it.) The function of kdb5_convert is to
> convert a V4 KDC database to a V5 database --- this is not very useful
> if you don't have an existing V4 KDC database. :-)
What about the other case I reported in kadmin/kpasswd? Should it be
compiled with K4LIB=-l$(DES425LIB) or not?
Thanks,
/Hugh
