"Henry B. Hotz" <hotz@jpl.nasa.gov> writes:
> I'm still testing, but basically it looks like if you have kerberos 4 then
> you need to disable use of the system crypt routines. This *should* be
> handled in the configure stuff.
That's fairly unpleasant, since it's not out of the question that a
given site might need to support both auth methods to cope with varying
clients.
> The function des_encrypt exists in both the KTH kerberos and the system
> crypt libraries with different arguments.
Not everywhere --- there's no such routine in my crypt library, for
instance. I would not like to see kerberos + crypt disabled everywhere
because it does not work on your machine.
Ideally we'd need an autoconf test to discover whether kerberos and
crypt libraries are compatible on a given machine, and an autoconf
--with switch to allow the user to decide which one to include if
they're not. Do you have any ideas about a simple way to check whether
this problem exists on a given platform?
regards, tom lane