Date: Wed, 11 Mar 2015 12:01:26 -0700 From: Paul Hoffman <paul.hoffman@vpnc.org> To: Gregory Shapiro <gshapiro@freebsd.org> Cc: freebsd security <freebsd-security@freebsd.org> Subject: Re: sendmail broken by libssl in current Message-ID: <F4FA7F6D-BB64-41CB-A6E1-3670C0F17870@vpnc.org> In-Reply-To: <20150311161549.GB16749@C02KM089FFRR.corp.proofpoint.com> References: <54FFE774.50103@freebsd.org> <alpine.BSO.2.20.1503110042030.28688@morgaine.local> <20150311161549.GB16749@C02KM089FFRR.corp.proofpoint.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 11, 2015, at 9:15 AM, Gregory Shapiro <gshapiro@freebsd.org> wrote: > 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? 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. --Paul Hoffman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F4FA7F6D-BB64-41CB-A6E1-3670C0F17870>