This is exactly similar to what I am looking for. I am using 1.0.2J version and there are some changes in the next version onwards that causes problems in SSL connections to older versions when DH key = 256 bytes are used. For backward compatibility reasons, I need to continue supporting 256 bytes DH keys for some more time and hence I want to stay on 1.0.2J version for now.
Anyways, Thanks for sharing the details.
Thanks,
Shiva
On Tue, 14 Jul 2020 at 19:03, Benjamin Kaduk <bkaduk@xxxxxxxxxx> wrote:
On Tue, Jul 14, 2020 at 04:58:38PM +0200, shivaramakrishna chakravarthula wrote:
> Hi,
>
> I have compatibility issues for my application with new versions of OpenSSL
> and I want to use the older version of OpenSSL with my application. So, I
> want to link my application with an OpenSSL library built with the custom
> name so that it works fine on all systems and I can be assured of using the
> desired OpenSSL version. I am using RPATH to locate the libraries in
> runtime and I want to make sure my libraries don't conflict with existing
> libraries.
How old is this "older version"?
The functionality you want sounds exactly like the "variant SONAMEs introduced
in commit https://github.com/openssl/openssl/commit/822b5e2645a99bea15329bd66c9723c7e7119cdb
but that's only in 1.1.0g and later.
-Ben
