Re: Compiling OpenSSL shared libraries with custom name on Unix platforms

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxx> wrote:
> From: openssl-users <openssl-users-bounces@xxxxxxxxxxx> 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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux