Compiling OpenSSL shared libraries with custom name on Unix platforms

[shivaramakrishna chakravarthula]

That was something I have tried initially until I had problems with FIPS
mode. I have compiled OpenSSL with FIPS support. But, I see FIPS self-tests
failing when I link my application with OpenSSL static libraries.

On Tue, 14 Jul 2020 at 17:57, Michael Wojcik <Michael.Wojcik at microfocus.com>
wrote:

> > From: openssl-users <openssl-users-bounces at openssl.org> On Behalf Of
> shivaramakrishna chakravarthula
> > Sent: Tuesday, 14 July, 2020 08:59
>
> > 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.
>
> The right way to fix this, of course, is to fix your application so it
> works with a current, supported OpenSSL version.
>
> Failing that, it would be best to link OpenSSL statically into your
> application. Then you don't have to worry about shared object location, and
> no one else will be using your outdated OpenSSL.
>
> --
> Michael Wojcik
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mta.openssl.org/pipermail/openssl-users/attachments/20200714/8ba938d4/attachment.html>