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 GENERIC#1 VIA Samuel 2 ("CentaurHauls" 686-class)
$ pkg_info | grep sasl
cyrus-sasl-2.1.20p4 RFC 2222 SASL (Simple Authentication and Security
Layer)
$ /usr/local/sbin/saslauthd -v
saslauthd 2.1.20
authentication mechanisms: getpwent kerberos5 rimap
$ ps aux | grep sasl
root 11222 0.0 0.3 552 1400 ?? Is 18Jan06 0:42.77
/usr/local/sbin/saslauthd -a kerberos5
root 25347 0.0 0.3 552 1392 ?? I 18Jan06 0:42.86
/usr/local/sbin/saslauthd -a kerberos5
root 30503 0.0 0.3 540 1388 ?? I 18Jan06 0:42.79
/usr/local/sbin/saslauthd -a kerberos5
root 18372 0.0 0.3 548 1360 ?? I 18Jan06 0:42.83
/usr/local/sbin/saslauthd -a kerberos5
root 28944 0.0 0.3 548 1372 ?? I 18Jan06 0:42.86
/usr/local/sbin/saslauthd -a kerberos5
It works fine. No problem here... but I'm running 3.8-release+patches
--
Antoine
