On Wed, 1 Feb 2006, Andreas Vögele wrote:
I'm wondering how this is possible since the Kerberos include path in
saslauthd's configure script *is* wrong. The port in CVS only fixes
the include path in the top-level configure script.
Do you follow -current?
No.
$ uname -prsv
OpenBSD 3.8 GENER
Antoine Jacoutot <[EMAIL PROTECTED]> writes:
> On Wed, 1 Feb 2006, Andreas Vögele wrote:
>
>> Antoine Jacoutot writes:
>>
>>> Hi, this is just a quick fix to replace hard coded /usr/local/etc to
>>> ${SYSCONFDIR} from the saslauthd man page.
>>
>> Also, saslauthd is currently built without support
On Wed, 1 Feb 2006, Andreas Vögele wrote:
Antoine Jacoutot writes:
Hi, this is just a quick fix to replace hard coded /usr/local/etc to
${SYSCONFDIR} from the saslauthd man page.
Also, saslauthd is currently built without support for the kerberos5
authentication mechanism. Here's a patch th
Antoine Jacoutot writes:
> Hi, this is just a quick fix to replace hard coded /usr/local/etc to
> ${SYSCONFDIR} from the saslauthd man page.
Also, saslauthd is currently built without support for the kerberos5
authentication mechanism. Here's a patch that fixes the Kerberos
include path in sasla
Hi, this is just a quick fix to replace hard coded /usr/local/etc to
${SYSCONFDIR} from the saslauthd man page.
Regards,
--
Antoine
cyrus-sasl2.diff
Description: Binary data
