From owner-freebsd-security@FreeBSD.ORG  Wed Mar 11 16:15:54 2015
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
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 2A71B528;
 Wed, 11 Mar 2015 16:15:54 +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 121E2606;
 Wed, 11 Mar 2015 16:15:54 +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 t2BGFlCf001642
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Wed, 11 Mar 2015 09:15:52 -0700 (PDT)
 (envelope-from gshapiro@freebsd.org)
Date: Wed, 11 Mar 2015 09:15:49 -0700
From: Gregory Shapiro <gshapiro@freebsd.org>
To: Philip Guenther <pguenther@proofpoint.com>
Subject: Re: sendmail broken by libssl in current
Message-ID: <20150311161549.GB16749@C02KM089FFRR.corp.proofpoint.com>
References: <54FFE774.50103@freebsd.org>
 <alpine.BSO.2.20.1503110042030.28688@morgaine.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.BSO.2.20.1503110042030.28688@morgaine.local>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Mailman-Approved-At: Wed, 11 Mar 2015 17:14:33 +0000
Cc: freebsd security <freebsd-security@freebsd.org>,
 Julian Elischer <julian@freebsd.org>
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Mar 2015 16:15:54 -0000

First, thank you Philip for jumping on this.  Much appreciated.

> This wonderful change (cough) to include SSL_OP_TLSEXT_PADDING in 
> SSL_OP_ALL was addressed in sendmail 8.15.1, which explicitly removes 
> SSL_OP_TLSEXT_PADDING from the default ClientSSLOptions value if that 
> #define exists.  I believe Greg is working on importing that to FreeBSD.

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?