Date: Fri, 26 Jun 2020 08:30:47 -0700 From: John Baldwin <jhb@FreeBSD.org> To: Benjamin Kaduk <bjkfbsd@gmail.com>, Gordon Tetlow <gordon@freebsd.org> Cc: src-committers <src-committers@freebsd.org>, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r362620 - head/secure/lib/libcrypto Message-ID: <82448b9f-b64f-73b2-37b9-1ccc9f7876aa@FreeBSD.org> In-Reply-To: <CAJ5_RoB5KCWZ1jvjx1BiGPVMNW6XBOgn03nEnMStqS00fdHmNA@mail.gmail.com> References: <202006251935.05PJZbJ2077013@repo.freebsd.org> <CAJ5_RoB5KCWZ1jvjx1BiGPVMNW6XBOgn03nEnMStqS00fdHmNA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/25/20 2:30 PM, Benjamin Kaduk wrote: > On Thu, Jun 25, 2020 at 12:35 PM Gordon Tetlow <gordon@freebsd.org> wrote: > >> Author: gordon >> Date: Thu Jun 25 19:35:37 2020 >> New Revision: 362620 >> URL: https://svnweb.freebsd.org/changeset/base/362620 >> >> Log: >> Revert OPENSSL_NO_SSL3_METHOD to keep ABI compatibility. >> >> This define caused a couple of symbols to disappear. To keep ABI >> compatibility, we are going to keep the symbols exposed, but leave SSLv3 >> as >> not in the default config (this is what OPENSSL_NO_SSL3 achieves). The >> ramifications of this is an application can still use SSLv3 if it >> specifically calls the SSLv3_method family of APIs. >> >> > I think I've seen some distros that keep the functinos around but just have > them always return failure. I think this is sensible for 13.0. It might even be something we could MFC to 12.x, but certainly for 13.0. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82448b9f-b64f-73b2-37b9-1ccc9f7876aa>