From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 15:28:04 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C60203AA for ; Thu, 25 Sep 2014 15:28:04 +0000 (UTC) Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 96819D6C for ; Thu, 25 Sep 2014 15:28:04 +0000 (UTC) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by gateway2.nyi.internal (Postfix) with ESMTP id 8069B24DA for ; Thu, 25 Sep 2014 11:28:03 -0400 (EDT) Received: from web6 ([10.202.2.216]) by compute2.internal (MEProxy); Thu, 25 Sep 2014 11:28:03 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:in-reply-to :references:subject:date; s=smtpout; bh=kALd1AFSROGJCXvOsqjZwPwc JDE=; b=Z+goV2Zy+DTdiC7lcbh3myeeYIXI3Mwmns15PHOYPiu0+fAlqCzx8pXe 29902vQ/eUXk7+ThmioG21Oc0Inr53sr00Vc9o6Q5NTW4BOIG6EclmXmaAMZBVm8 WHY90NMN7e+dniPe2s6z33cbiN37KQ8cTLozRdfASXz8U7zjg/w= Received: by web6.nyi.internal (Postfix, from userid 99) id 2D7E757044; Thu, 25 Sep 2014 11:28:03 -0400 (EDT) Message-Id: <1411658883.3420802.171710921.16657E93@webmail.messagingengine.com> X-Sasl-Enc: RYb4YtFafv+II0OKVEhRcILCXI10iQapBaRDauXMSye1 1411658883 From: Mark Felder To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-cad53418 In-Reply-To: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> References: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> Subject: Re: 10.1 BETA2 World - Breaks saslauthd Date: Thu, 25 Sep 2014 10:28:03 -0500 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2014 15:28:04 -0000 On Thu, Sep 25, 2014, at 10:04, Dimitry Andric wrote: > On 25 Sep 2014, at 16:54, Tim Daneliuk wrote: > > I've seen this behavior over the last week or two when I try to upgrade > > to latest stable sources. Currently just installed kernel and world for: > > > > /usr/src>svn info > > Path: . > > Working Copy Root Path: /usr/src > > URL: svn://svn.freebsd.org/base/stable/10 > > Relative URL: ^/stable/10 > > Repository Root: svn://svn.freebsd.org/base > > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > > Revision: 272095 > > Node Kind: directory > > Schedule: normal > > Last Changed Author: peter > > Last Changed Rev: 272078 > > Last Changed Date: 2014-09-24 14:30:36 -0500 (Wed, 24 Sep 2014) > > > > This breaks saslauthd - it demands a password when sending mail, but then > > rejects it in every case. > > > > 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. > Hmm sounds like we need a bug report to request that an example pam.d/smtp be provided and an UPDATING entry perhaps.