Date: Thu, 25 Sep 2014 10:12:43 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: Dimitry Andric <dim@FreeBSD.org> Cc: FreeBSD stable <freebsd-stable@freebsd.org>, =?windows-1252?Q?Dag-Erl?= =?windows-1252?Q?ing_Sm=F8rgrav?= <des@FreeBSD.org> Subject: Re: 10.1 BETA2 World - Breaks saslauthd Message-ID: <542430EB.1040804@tundraware.com> In-Reply-To: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> References: <b492e700f57a52e21f7755e6d01bd863.squirrel@www.tundraware.com> <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/25/2014 10:04 AM, Dimitry Andric wrote: <SNIP> >> If I just install a new kernel, everything is fine. But if I install >> world, that's when the problem shows up. I've tried a full reinstall of >> cygnus sasls and the daemon is running. >> >> Ideas on how to chase this down/fix, would be appreciated... > > It is probably caused by this MFC: http://svnweb.freebsd.org/changeset/base/271766 > > To make saslauthd work again, you need to specify a correct PAM policy > file in /usr/local/etc/pam.d for your service, most likely "smtp" in > this case. E.g., create a file /usr/local/etc/pam.d/smtp, containing at > least: > > auth required pam_unix.so no_warn try_first_pass > account required pam_unix.so > session required pam_permit.so > password required pam_permit.so > > Optionally, add a line: > > auth required pam_group.so luser group=smtp-users fail_safe > > to allow only members of the smtp-users group to authenticate > successfully. > > -Dimitry > Yup, that worked. Thanks! Now, for those of us less than smart, could you explain why this was necessary in context of that MFC? Thanks very much ... -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?542430EB.1040804>