* Jittinan Suwanrueangsri <jittinan2@xxxxxxxxx>:
> Hi All
>
> I have installed Cyrus SASL 2.1.22-4 on RHEL 5.3 from rpm but after
> I try to run sasl2-sample-server it seem that a server does not read
> configuration file from default path "/usr/lib/sasl2".
> How should I fix this problem?
>
> configuration file is /usr/lib/sasl2/testsasl.conf. Here is it's
> content(only one line):
The name must be /usr/lib/sasl2/sample.conf.
It's the sample-server. It sends 'sample' as application name. libsasl
searches for $application_name . '.conf'.
>
>
> pwcheck_method: saslauthd
>
>
> for make sure that saslauthd can work correctly
>
> output from saslauthd:
> # saslauthd -a shadow -d
> saslauthd[8822] :main : num_procs : 5
> saslauthd[8822] :main : mech_option: NULL
> saslauthd[8822] :main : run_path : /var/run/saslauthd
> saslauthd[8822] :main : auth_mech : shadow
> saslauthd[8822] :ipc_init : using accept lock file:
> /var/run/saslauthd/mux.accept
> saslauthd[8822] :detach_tty : master pid is: 0
> saslauthd[8822] :ipc_init : listening on socket:
> /var/run/saslauthd/mux
> saslauthd[8822] :main : using process model
> saslauthd[8823] :get_accept_lock : acquired accept lock
> saslauthd[8822] :have_baby : forked child: 8823
> saslauthd[8822] :have_baby : forked child: 8824
> saslauthd[8822] :have_baby : forked child: 8825
> saslauthd[8822] :have_baby : forked child: 8826
> saslauthd[8823] :rel_accept_lock : released accept lock
> saslauthd[8824] :get_accept_lock : acquired accept lock
> saslauthd[8823] :do_auth : auth success: [user=sampleuser]
> [service=imap] [realm=] [mech=shadow]
> saslauthd[8823] :do_request : response: OK
>
>
> output from testsasl:
>
> # testsaslauthd -u sampleuser -p password
> 0: OK "Success."
> #
>
>
> output from sasl2-sample-server:
>
> # sasl2-sample-server -s testsasl -m PLAIN
> trying 10, 1, 6
> trying 2, 1, 6
> bind: Address already in use
> accepted new connection
> send: {5}
> PLAIN
> recv: {5}
> PLAIN
> recv: {1}
> Y
> recv: {30}
> [0][0]0b99boyomN
> starting SASL negotiation: user not foundclosing connection
>
>
> output from sasl2-sample-client:
>
> # sasl2-sample-client -s testsasl -m PLAIN localhost
> receiving capability list... recv: {5}
> PLAIN
> PLAIN
> please enter an authentication id: sampleuser
> please enter an authorization id: sampleuser
> Password:
> send: {5}
> PLAIN
> send: {1}
> Y
> send: {30}
> sampleuser[0]sampleuser[0]password
> authentication failed
> closing connection
> #
>
> After I execute sasl2-sample-client command .Output from saslauthd
> is still not change like it does not recieve any authentication
> request from sasl2-sample-server.As shown below.
>
> output from saslauthd:
> # saslauthd -a shadow -d
> saslauthd[8822] :main : num_procs : 5
> saslauthd[8822] :main : mech_option: NULL
> saslauthd[8822] :main : run_path : /var/run/saslauthd
> saslauthd[8822] :main : auth_mech : shadow
> saslauthd[8822] :ipc_init : using accept lock file:
> /var/run/saslauthd/mux.accept
> saslauthd[8822] :detach_tty : master pid is: 0
> saslauthd[8822] :ipc_init : listening on socket:
> /var/run/saslauthd/mux
> saslauthd[8822] :main : using process model
> saslauthd[8823] :get_accept_lock : acquired accept lock
> saslauthd[8822] :have_baby : forked child: 8823
> saslauthd[8822] :have_baby : forked child: 8824
> saslauthd[8822] :have_baby : forked child: 8825
> saslauthd[8822] :have_baby : forked child: 8826
> saslauthd[8823] :rel_accept_lock : released accept lock
> saslauthd[8824] :get_accept_lock : acquired accept lock
> saslauthd[8823] :do_auth : auth success: [user=sampleuser]
> [service=imap] [realm=] [mech=shadow]
> saslauthd[8823] :do_request : response: OK
>
>
>
>
>
>
>
