Date: Fri, 11 Dec 2020 12:19:34 GMT From: Martin Simmons <martin@lispworks.com> To: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-20:33.openssl Message-ID: <202012111219.0BBCJYSf000629@higson.cam.lispworks.com> In-Reply-To: <2AF24633-7E9F-4B92-8E99-6A81CD9D3AF8@lastsummer.de> (message from Franco Fichtner on Fri, 11 Dec 2020 12:44:17 %2B0100) References: <20201209230300.03251CA1@freefall.freebsd.org> <20201211064628.GM31099@funkthat.com> <202012111138.0BBBc2Eq006002@higson.cam.lispworks.com> <2AF24633-7E9F-4B92-8E99-6A81CD9D3AF8@lastsummer.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> On Fri, 11 Dec 2020 12:44:17 +0100, Franco Fichtner said: > > > On 11. Dec 2020, at 12:38 PM, Martin Simmons <martin@lispworks.com> wrote: > > > >>>>>> On Thu, 10 Dec 2020 22:46:28 -0800, John-Mark Gurney said: > >> > >> What are peoples thoughts on how to address the support mismatch between > >> FreeBSD and OpenSSL? And how to address it? > > > > Maybe it would help a little if the packages on pkg.FreeBSD.org all used the > > pkg version of OpenSSL? Currently, it looks like you have build your own > > ports if you want that. > > This pretty much breaks LibreSSL ports usage for binary package consumers. I'm talking about the binary packages from pkg.FreeBSD.org. Don't they always use the base OpenSSL at the moment? __Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202012111219.0BBCJYSf000629>