From: Joakim Ryden (jryden at thebox dot our-own dot net)
Date: Mon Dec 15 2003 - 11:20:22 EST
Thanks Igor!
I'm still getting the same thing. :-/
--Jo
On 12/15/03 5:32 AM Igor Brezac wrote:
> Download the latest lak.c
> (https://bugzilla.andrew.cmu.edu/cgi-bin/cvsweb.cgi/~checkout~/src/sasl/saslauthd/lak.c?rev=1.36)
> and recompile saslauthd. This should fix it for you.
>
> -Igor
>
> On Mon, 15 Dec 2003, Joakim Ryden wrote:
>
>
>>Hey everyone -
>>
>>I just upgraded a system from FreeBSD 4 to FreeBSD 5 and somewhere along
>>the way something must have gotten messed up for sasl(authd). It's
>>installed/compiled from the ports collection (version 2.1.17) using
>>OpenLDAP 2.1.23 libraries. When I try authenticating against it using
>>the testsaslauthd program I get this on the console where I started it:
>>
>>
>>[root at thebox saslauthd]# saslauthd -n 2 -a ldap -d
>>saslauthd[10559] :main : num_procs : 2
>>saslauthd[10559] :main : mech_option: NULL
>>saslauthd[10559] :main : run_path : /var/state/saslauthd
>>saslauthd[10559] :main : auth_mech : ldap
>>saslauthd[10559] :ipc_init : using accept lock file:
>>/var/state/saslauthd/mux.accept
>>saslauthd[10559] :detach_tty : master pid is: 0
>>saslauthd[10559] :ipc_init : listening on socket:
>>/var/state/saslauthd/mux
>>saslauthd[10559] :main : using process model
>>saslauthd[10559] :have_baby : forked child: 10560
>>saslauthd[10560] :get_accept_lock : acquired accept lock
>>saslauthd[10559] :get_accept_lock : acquired accept lock
>>saslauthd[10560] :rel_accept_lock : released accept lock
>>saslauthd in free(): error: chunk is already free
>>saslauthd[10559] :handle_sigchld : child exited: 10560
>>saslauthd[10559] :rel_accept_lock : released accept lock
>>saslauthd[10559] :get_accept_lock : acquired accept lock
>>saslauthd[10559] :rel_accept_lock : released accept lock
>>saslauthd in free(): error: chunk is already free
>>Abort trap (core dumped)
>>
>>My saslauthd configuration file contains:
>>
>>ldap_version: 3
>>ldap_use_sasl: no
>>ldap_servers: ldap://10.0.0.19/
>>ldap_bind_dn: cn=admin,dc=our-own,dc=net
>>ldap_bind_pw: verysecret
>>ldap_auth_method: custom
>>ldap_sasl_mech: PLAIN LOGIN
>>ldap_search_base: ou=MailUsers,dc=our-own,dc=net
>>ldap_filter: uid=%u
>>ldap_scope: one
>>
>>Does anyone have any thoughts on what might be going on??
>>
>>--Jo
>>
>
>
|
|
|