Date: Wed, 11 Mar 2015 12:49:05 -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: <3FEBF8E9-BB5B-403F-9648-A5F7CB60F9AB@vpnc.org> In-Reply-To: <20150311192514.GS16749@C02KM089FFRR.corp.proofpoint.com> References: <54FFE774.50103@freebsd.org> <alpine.BSO.2.20.1503110042030.28688@morgaine.local> <20150311161549.GB16749@C02KM089FFRR.corp.proofpoint.com> <F4FA7F6D-BB64-41CB-A6E1-3670C0F17870@vpnc.org> <20150311192514.GS16749@C02KM089FFRR.corp.proofpoint.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 11, 2015, at 12:25 PM, Gregory Shapiro <gshapiro@freebsd.org> = wrote: >=20 >>> 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. >>>=20 >>> 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? >>=20 >> 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. >=20 > My intent is to patch sendmail, not OpenSSL, with a change that is = already part of a newer sendmail release. Ah, that wasn't clear from the thread, sorry. Sure, patching Sendmail = for this seems fine. Thanks! --Paul Hoffman=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FEBF8E9-BB5B-403F-9648-A5F7CB60F9AB>