From owner-freebsd-security@FreeBSD.ORG Fri May 15 18:34:34 2015 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 969DC9C8 for ; Fri, 15 May 2015 18:34:34 +0000 (UTC) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8570911F6 for ; Fri, 15 May 2015 18:34:34 +0000 (UTC) Date: Fri, 15 May 2015 11:34:33 -0700 (PDT) From: Roger Marquis To: freebsd-security@freebsd.org Subject: Re: Forums.FreeBSD.org - SSL Issue? In-Reply-To: <1431705766.3563083.269738569.0FA82C3E@webmail.messagingengine.com> References: <2857899F-802E-4086-AD41-DD76FACD44FB@modirum.com> <05636D22-BBC3-4A15-AC44-0F39FB265CDF@patpro.net> <20150514193706.V69409@sola.nimnet.asn.au> <5554879D.7060601@obluda.cz> <1431697272.3528812.269632617.29548DB0@webmail.messagingengine.com> <20150515152220.C0CC7689@hub.freebsd.org> <1431705766.3563083.269738569.0FA82C3E@webmail.messagingengine.com> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 May 2015 18:34:34 -0000 Mark Felder wrote: >> Another option is a second openssl port, one that overwrites base and >> guarantees compatibility with RELEASE. Then we could at least have all >> versions of openssl in vuln.xml (not that that's been a reliable >> indicator of security of late). >> > > This will never work. You can't guarantee compatibility with RELEASE and > upgrade it too. How do you figure? RedHat does exactly that with every backport, and they do it for the life of a release. Roger