Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Dec 2020 16:54:04 -0500
From:      mike tancsa <mike@sentex.net>
To:        Dave Hayes <dave@jetcafe.org>, jerry@seibercom.net
Cc:        FreeBSD <freebsd-questions@freebsd.org>
Subject:   Re: Patches for OpenSSL
Message-ID:  <7e5c3b15-e9a4-3b1e-aef6-04e6d7283136@sentex.net>
In-Reply-To: <20201210125522.7e52d804@bigus.dream-tech.com>
References:  <267201d6ceeb$52ffcaa0$f8ff5fe0$@seibercom.net> <20201210125522.7e52d804@bigus.dream-tech.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 12/10/2020 3:55 PM, Dave Hayes wrote:
> On Thu, 10 Dec 2020 06:55:15 -0500
> <jerry@seibercom.net> wrote:
>> I just read "FreeBSD Security Advisory FreeBSD-SA-20:33.openssl". I found the
>> following part of the message quite troubling.
> Not just troubling, but enough to cause me to build base without openssl for
> the forseeable future.  

When we were migrating servers from RELENG_11 to RELENG_12, it was a bit
of work making sure ports/packages/custom apps that were linked against
the older OpenSSL worked with the newer one as its not a simple
replacement due to API breakage.  I am guessing a few things in the base
might have issues as well that wont allow for a simple drop in
replacement of the new OpenSSL.  Its all quite doable, but its a bit of work

    ---Mike





Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?7e5c3b15-e9a4-3b1e-aef6-04e6d7283136>