Never saw a followup on this.
I'd suggest krb5_init_context() since it's the first thing any
Kerberos app needs to do, and the returned context value is used on
99% of all other calls. That's assuming that there aren't other
kerberos checks that make it unnecessary of course.
On Jul 2, 2006, at 8:39 PM, Tom Lane wrote:
> James Gates <James.Gates@Sun.COM> writes:
>> Does anyone know why the check for krb5_encrypt() exists in configure
>> when the code doesn't use it?
>
> At the time it was chosen, it was probably a reasonable choice of
> function to probe for to make sure Kerberos libraries are present.
> Do you have a better suggestion?
>
> regards, tom lane
------------------------------------------------------------------------
----
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz@jpl.nasa.gov, or hbhotz@oxy.edu
