Bug#398657: slapd's sasl looks in /usr/lib/sasl2/slapd.conf for its configuration

2006-12-09 Thread Matthijs Mohlmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 tag 398657 + patch thanks Here a patch which adds a callback for the sasl context to get the path of the sasl configuration file. It also looks in the old path (/usr/lib/sasl2) I think applying this for Etch doesn't harm. See for more information:

Bug#398657: slapd's sasl looks in /usr/lib/sasl2/slapd.conf for its configuration

2006-12-09 Thread Matthijs Mohlmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Hm my patch wasn't ok, an updated is attached. The previous patch had the wrong configuration file location. And used the wrong callback function to set the configuration path. (My first testing did go ok, but I didn't remove the

Bug#398657: slapd's sasl looks in /usr/lib/sasl2/slapd.conf for its configuration

2006-11-14 Thread Peter Palfrader
Package: slapd Version: 2.3.27-1 Severity: normal When slapd is using the sasl authentication backend for simple authentication (userpassword: [EMAIL PROTECTED]), it looks in /usr/lib/sasl2/slapd.conf for the configuration file. e.g: | krb:~# cat /usr/lib/sasl2/slapd.conf | pwcheck_method: