Date: Sat, 13 Oct 2018 23:00:18 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: FreeBSD current <freebsd-current@FreeBSD.org> Cc: re@FreeBSD.org Subject: Re: OpenSSL 1.1.1 libssl.so version number Message-ID: <tkrat.2bc2d671f8dc3fb8@FreeBSD.org> In-Reply-To: <tkrat.3c3bfd84a6c58d9a@FreeBSD.org> References: <tkrat.3c3bfd84a6c58d9a@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12 Oct, Don Lewis wrote:
> Prior to the OpenSSL 1.1.1 import, the base OpenSSL library was
> /usr/lib/libssl.so.8. The security/openssl port (1.0.2p) installed
> ${LOCALBASE}/lib/ilbssl.so.9 and the security/openssl-devel port
> (1.1.0i) installed ${LOCALBASE}/lib/libssl.so.11. After the import, the
> base OpenSSL library is /usr/lib/libssl.so.9. Now if you build ports
> with DEFAULT_VERSIONS+=ssl=openssl, the library that actually gets used
> is ambiguous because there are now two different versions of libssl.so
> (1.0.2p and 1.1.1) with the same shared library version number.
>
> I stumbled across this when debugging a virtualbox-ose configure
> failure. The test executable was linked to the ports version of
> libssl.so but rtld chose the base libssl.so at run time.
It looks to me like the base libssl.so version needs to get moved to a
value that doesn't collide with ports, perhaps 12. These are the
library version numbers currently used by the various ssl ports:
boringssl 1
openssl 9
openssl-devel 10
openssl111 11
libressl 43
libressl-devel 44
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?tkrat.2bc2d671f8dc3fb8>