[572] in Kerberos-V5-bugs
Configure Suggestions for Kerberos 5.4.1
daemon@ATHENA.MIT.EDU (Theodore Ts'o)
Sat Jul 9 14:14:01 1994
Date: Sat, 9 Jul 94 14:13:20 -0400
From: Theodore Ts'o <tytso@MIT.EDU>
To: DEEngert@anl.gov
Cc: KRB5-BUGS@MIT.EDU, AUTH-PILOT@ES.NET
In-Reply-To: "Doug Engert"'s message of Fri, 01 Jul 94 10:58:36 CDT <9407011559.AA04114@MIT.EDU>
Date: Fri, 01 Jul 94 10:58:36 CDT
From: "Doug Engert" <DEEngert@anl.gov>
o The --with-krb4 is not very flexible. With the Imake I could
use the old /usr/athena/... libs built with Kerberos 4, or the
libkrb425.a and libdes425.a. With the configure it appears to
use a combination of libkrb.a and libdes425.a. I would prefer
to use the krb425 stuff, since I don't want to have to build
Kerberos 4 for any new platforms.
(Sorry for the delay in getting back to you; I've away in Germany for a
week, so I'm only now getting back to answering mail...)
It seems that you don't understand what the krb425 library are used for.
What they do is present a simplified krb4 API, but uses the krb5
protocol. The rather dubious idea was that it might allow people with
krb4 applications to simply link with the krb425 library as a simple way
to port an application to use the Kerberos V5 protocol.
It is **not** a substitute for the libkrb.a library, which is used when
give the --with-krb4 argument to configure. If you give this argument,
you are requesting that the Kerberos build have backwards compatibility
with the Kerberos V5 protocol. So, using libkrb425.a as a substitute
for libkrb.a simply doesn't work.
Note that unless you need the krb4 compatibility, there's no need to
bother with linking in libkrb.a anyway. Since you apparently haven't
noticed that linking with libkrb425.a results in a binary which will
completely fail to work if you try to use its V4 backwards compatibility
features, I conjecture that you don't actually need it. If you really
do need the compatibility features, then I'm afraid for now, you will
need to build Kerberos V4 separately.
At some point in the future, we may consider including the V4 library
into the V5 distribution. But, we currently have much higher priority
items which we'd like to accomplish first.
- Ted
