Date: Sat, 13 Oct 2018 14:02:37 -0400 From: Daniel Eischen <deischen@freebsd.org> To: Cy Schubert <Cy.Schubert@cschubert.com> Cc: Don Lewis <truckman@FreeBSD.org>, FreeBSD current <freebsd-current@FreeBSD.org>, re@FreeBSD.org Subject: Re: OpenSSL 1.1.1 libssl.so version number Message-ID: <0F7EB379-8C52-478A-AA5A-AC4257E5B70A@freebsd.org> In-Reply-To: <201810130258.w9D2wbIh042892@slippy.cwsent.com> References: <201810130258.w9D2wbIh042892@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Oct 12, 2018, at 10:58 PM, Cy Schubert <Cy.Schubert@cschubert.com> wrot=
e:
>=20
> In message <tkrat.3c3bfd84a6c58d9a@FreeBSD.org>, Don Lewis writes:
>> 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+=3Dssl=3Dopenssl, the library that actually gets us=
ed
>> 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.
>>=20
>> 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.
>=20
> This is also the issue with ports-mgmt/pkg on a system that still=20
> requires OpenSSL 1.0.2 from ports in order to support an old client.
>=20
> cwfw# pkg info
> ld-elf.so.1: /usr/local/lib/libcrypto.so.9: version OPENSSL_1_1_0=20
> required by /usr/local/lib/libpkg.so.4 not defined
> cwfw#=20
>=20
> If I remove security/openssl, the above issue is resolved however the=20
> old client, which should be replaced next year, fails to communicate=20
> with the server. The classic rock & a hard place scenario.
Not saying this is a real solution for the general problem, but can you use a=
libmap.conf entry to work around this?
--
DE=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0F7EB379-8C52-478A-AA5A-AC4257E5B70A>