Date: Sat, 27 Sep 2014 11:07:04 -0400 From: Brandon Allbery <allbery.b@gmail.com> To: Dimitry Andric <dim@freebsd.org> Cc: freebsd-stable <freebsd-stable@freebsd.org>, Jan Bramkamp <crest@rlwinm.de> Subject: Re: 10.1 BETA2 World - Breaks saslauthd Message-ID: <CAKFCL4V9yY17H15j=R9KKbKeK_zU64ysn4caqF9qem8JwPviCw@mail.gmail.com> In-Reply-To: <A4E96B09-AEF9-46B3-A812-1DFB7EB6D90B@FreeBSD.org> References: <b492e700f57a52e21f7755e6d01bd863.squirrel@www.tundraware.com> <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> <5426C3F3.3040404@rlwinm.de> <A4E96B09-AEF9-46B3-A812-1DFB7EB6D90B@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 27, 2014 at 10:36 AM, Dimitry Andric <dim@freebsd.org> wrote: > > If I remember correctly saslauthd -a pam is hardcoded to always use the > > PAM service "imap". > > No, the service name is received from the SASL client that connects to > /var/run/saslauthd/mux. In case of postfix, the default service name is > "smtp". Quoting from postconf(5): > saslauthd isn't the core SASL entry point; it's a hack to export traditional password stores as SASL providers to cyrus-sasl. Last I checked, it didn't actually receive the service name from SASL. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKFCL4V9yY17H15j=R9KKbKeK_zU64ysn4caqF9qem8JwPviCw>