Hi, see below Henrique de Moraes Holschuh wrote:
>On Fri, 23 Sep 2005, Achim Schaefer wrote: > > >>the provied /etc/default/saslauthd has the following lines: >># You must specify the authentication mechanisms you wish to use. >># This defaults to "pam" for PAM support, but may also include >># "shadow" or "sasldb", like this: >># MECHANISMS="pam shadow" >> >>Looks like the deamon can handle more than one auth method, but: >>saslauthd -h >>usage: saslauthd [options] >> >>option information: >> -a <authmech> Selects the authentication mechanism to use. >> >>says clearly it can handle only one method. >>The second one is simply ignored. >> >> > >It should not be, and it used to work just fine in the past. Look at the >source code instead of usage messages. And try -a "method1 method2" too. > >Please reply with your findings. > > > I simply tried the following: (only one auth method) server:/home/achim# saslauthd -n 1 -d -a shadow saslauthd[2853] :main : num_procs : 1 saslauthd[2853] :main : mech_option: NULL saslauthd[2853] :main : run_path : /var/run/saslauthd saslauthd[2853] :main : auth_mech : shadow saslauthd[2853] :ipc_init : using accept lock file: /var/run/saslauthd/mux.accept saslauthd[2853] :detach_tty : master pid is: 0 saslauthd[2853] :ipc_init : listening on socket: /var/run/saslauthd/mux saslauthd[2853] :main : using process model saslauthd[2853] :get_accept_lock : acquired accept lock saslauthd[2853] :server_exit : pid file lock removed: /var/run/saslauthd/saslauthd.pid.lock saslauthd[2853] :ipc_cleanup : accept lock file removed: /var/run/saslauthd/mux.accept saslauthd[2853] :ipc_cleanup : socket removed: /var/run/saslauthd/mux saslauthd[2853] :server_exit : master exited: 0 Fine everything as expected Your suggestion (Am I right?): server:/home/achim# saslauthd -n 1 -d -a "shadow pam" saslauthd[2855] :set_auth_mech : unknown authentication mechanism: shadow pam Now without the quotes (this is the way /etc/init.d/saslauthd works (as far as I understood the script) server:/home/achim# saslauthd -n 1 -d -a shadow pam saslauthd[2857] :main : num_procs : 1 saslauthd[2857] :main : mech_option: NULL saslauthd[2857] :main : run_path : /var/run/saslauthd saslauthd[2857] :main : auth_mech : shadow saslauthd[2857] :ipc_init : using accept lock file: /var/run/saslauthd/mux.accept saslauthd[2857] :detach_tty : master pid is: 0 saslauthd[2857] :ipc_init : listening on socket: /var/run/saslauthd/mux saslauthd[2857] :main : using process model saslauthd[2857] :get_accept_lock : acquired accept lock saslauthd[2857] :server_exit : pid file lock removed: /var/run/saslauthd/saslauthd.pid.lock saslauthd[2857] :ipc_cleanup : accept lock file removed: /var/run/saslauthd/mux.accept saslauthd[2857] :ipc_cleanup : socket removed: /var/run/saslauthd/mux saslauthd[2857] :server_exit : master exited: 0 Fine he is using the first one, but not the last. Does this help you? Regards Achim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
