From owner-freebsd-questions@FreeBSD.ORG Sat Dec 6 08:39:34 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 32E96CED for ; Sat, 6 Dec 2014 08:39:34 +0000 (UTC) Received: from systemdatarecorder.org (mail.systemdatarecorder.org [54.246.96.61]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "localhost", Issuer "localhost" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A4F2632C for ; Sat, 6 Dec 2014 08:39:32 +0000 (UTC) Received: from nereid (82-181-158-75.bb.dnainternet.fi [82.181.158.75]) (authenticated bits=0) by systemdatarecorder.org (8.14.4/8.14.4/Debian-2ubuntu2.1) with ESMTP id sB68fUZT016577 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Sat, 6 Dec 2014 08:41:31 GMT Date: Sat, 6 Dec 2014 10:39:15 +0200 From: Stefan Parvu To: freebsd-questions@freebsd.org Subject: auth failed for pam saslauthd freebsd current Message-Id: <20141206103915.52ea705d4213fec971897aa7@systemdatarecorder.org> Organization: systemdatarecorder.org X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2014 08:39:34 -0000 Hi, Im trying to understand why I cant auth via pam using testsaslauthd. I have installed: * cyrus-sasl-2.1.26_9 * cyrus-sasl-saslauthd-2.1.26_1 SASL authentication server for cyrus-sasl2 and Im starting saslauthd in debug mode: Starting saslauthd. saslauthd[3219] :main : num_procs : 5 saslauthd[3219] :main : mech_option: NULL saslauthd[3219] :main : run_path : /var/run/saslauthd saslauthd[3219] :main : auth_mech : pam saslauthd[3219] :ipc_init : using accept lock file: /var/run/saslauthd/mux.accept saslauthd[3219] :detach_tty : master pid is: 0 saslauthd[3219] :ipc_init : listening on socket: /var/run/saslauthd/mux saslauthd[3219] :main : using process model saslauthd[3219] :have_baby : forked child: 3220 saslauthd[3220] :get_accept_lock : acquired accept lock saslauthd[3219] :have_baby : forked child: 3221 saslauthd[3219] :have_baby : forked child: 3222 saslauthd[3219] :have_baby : forked child: 3223 and then trying to test: testsaslauthd -u xxxx -p xxxx returns always: 0: NO "authentication failed" and in the saslauthd logs: saslauthd[3220] :rel_accept_lock : released accept lock saslauthd[3221] :get_accept_lock : acquired accept lock saslauthd[3220] :do_auth : auth failure: [user=sparvu] [service=imap] [realm=localhost] [mech=pam] [reason=PAM auth error] The saslauthd runs as: root 3231 0.0 0.1 47276 5176 4 S+ 10:38AM 0:00.01 /usr/local/sbin/saslauthd -d -a pam -m /var/run/saslauthd root 3232 0.0 0.1 47276 5176 4 S+ 10:38AM 0:00.00 /usr/local/sbin/saslauthd -d -a pam -m /var/run/saslauthd root 3233 0.0 0.1 47276 5172 4 S+ 10:38AM 0:00.00 /usr/local/sbin/saslauthd -d -a pam -m /var/run/saslauthd root 3234 0.0 0.1 47276 5172 4 S+ 10:38AM 0:00.00 /usr/local/sbin/saslauthd -d -a pam -m /var/run/saslauthd root 3235 0.0 0.1 47276 5172 4 S+ 10:38AM 0:00.00 /usr/local/sbin/saslauthd -d -a pam -m /var/run/saslauthd Anyone any ideas ? Many thanks, -- Stefan Parvu