[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [suse-security] cyrus-SASL - need help



Am Friday 18 November 2005 20:00 schrieb Milan Milosevic:

> > # saslauthd -da pam
> > Try it with testsaslauthd and check the Output in the other Window. Show
> > the Complete Messages.
>
> seenet-mtp:~ # saslauthd -da pam
> saslauthd[5273] :main            : num_procs  : 5
> saslauthd[5273] :main            : mech_option: NULL
> saslauthd[5273] :main            : run_path   : /var/run/sasl2/
> saslauthd[5273] :main            : auth_mech  : pam
> saslauthd[5273] :ipc_init        : using accept lock file:
> /var/run/sasl2//mux.accept saslauthd[5273] :detach_tty      : master pid
> is: 0
> saslauthd[5273] :ipc_init        : listening on socket: /var/run/sasl2//mux
> saslauthd[5273] :main            : using process model
> saslauthd[5274] :get_accept_lock : acquired accept lock
> saslauthd[5273] :have_baby       : forked child: 5274
> saslauthd[5273] :have_baby       : forked child: 5275
> saslauthd[5273] :have_baby       : forked child: 5276
> saslauthd[5273] :have_baby       : forked child: 5277
> saslauthd[5274] :rel_accept_lock : released accept lock
> saslauthd[5275] :get_accept_lock : acquired accept lock
> saslauthd[5274] :do_auth         : auth failure: [user=mmilan]
> [service=imap] [realm=] [mech=pam] [reason=PAM auth error]

Check your /etc/pam.d/imap. If it is not there check for a File "other" in 
your ./pam.d/.

I don't see "size read" Errors, or similar.

> I tried same for saslauthd -da shadow (method I used) and result is:
>
> seenet-mtp:~ # saslauthd -da shadow
> saslauthd[5319] :main            : num_procs  : 5
> saslauthd[5319] :main            : mech_option: NULL
> saslauthd[5319] :main            : run_path   : /var/run/sasl2/
> saslauthd[5319] :main            : auth_mech  : shadow
> saslauthd[5319] :ipc_init        : using accept lock file:
> /var/run/sasl2//mux.accept saslauthd[5319] :detach_tty      : master pid
> is: 0
> saslauthd[5319] :ipc_init        : listening on socket: /var/run/sasl2//mux
> saslauthd[5319] :main            : using process model
> saslauthd[5320] :get_accept_lock : acquired accept lock
> saslauthd[5319] :have_baby       : forked child: 5320
> saslauthd[5319] :have_baby       : forked child: 5321
> saslauthd[5319] :have_baby       : forked child: 5322
> saslauthd[5319] :have_baby       : forked child: 5323
> saslauthd[5320] :rel_accept_lock : released accept lock
> saslauthd[5321] :get_accept_lock : acquired accept lock
> saslauthd[5319] :handle_sigchld  : child exited: 5320

Did you run testsaslauthd with that?

-- 
	Andreas

-- 
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@xxxxxxxx
Security-related bug reports go to security@xxxxxxx, not here