From owner-freebsd-security@FreeBSD.ORG Wed Mar 11 19:25:17 2015 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EC21E9F2 for ; Wed, 11 Mar 2015 19:25:17 +0000 (UTC) Received: from zim.gshapiro.net (zim.gshapiro.net [IPv6:2001:4f8:3:36::224]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.gshapiro.net", Issuer "Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D2E8BEEA for ; Wed, 11 Mar 2015 19:25:17 +0000 (UTC) Received: from C02KM089FFRR.corp.proofpoint.com (mx2.proofpoint.com [208.86.202.10]) (authenticated bits=0) by zim.gshapiro.net (8.14.9/8.14.9) with ESMTP id t2BJPEPW019255 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 11 Mar 2015 12:25:17 -0700 (PDT) (envelope-from gshapiro@freebsd.org) Date: Wed, 11 Mar 2015 12:25:14 -0700 From: Gregory Shapiro To: Paul Hoffman Subject: Re: sendmail broken by libssl in current Message-ID: <20150311192514.GS16749@C02KM089FFRR.corp.proofpoint.com> References: <54FFE774.50103@freebsd.org> <20150311161549.GB16749@C02KM089FFRR.corp.proofpoint.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Mailman-Approved-At: Wed, 11 Mar 2015 20:12:05 +0000 Cc: freebsd security X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 19:25:18 -0000 > > sendmail 8.15.1 is imported into the vendor area but not merged due to an incompatible change that is being moved into a run-time configuration variable in 8.15.2. Rather than expose the FreeBSD populate to the churn from that change, I am skipping 8.15.1 and will import 8.15.2. > > > > That being said, I can certainly make the local fix that Philip mention to take care of the padding issue. Is the new libssl in 11-CURRENT going to be/already been MFC'ed to other branches? > > I'm still *really* hesitant for us to be patching OpenSSL for a bug on a middlebox vendor's system that already has a fix. My intent is to patch sendmail, not OpenSSL, with a change that is already part of a newer sendmail release.