On Tue, Jul 14, 2020 at 09:08:10PM +0200, shivaramakrishna chakravarthula wrote:
> 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
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
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 b
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
wrote:
> > From: openssl-users On B
> From: openssl-users 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 wit
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 usin
> From: shivaramakrishna chakravarthula
>
> Is it possible to compile OpenSSL shared libraries with custom
> names on Linux/ Unix platforms to avoid conflicts with installed
> OpenSSL libraries?
> I have tried to modify the SHLIB_EXT in Configure script but it is
> not working. I am sure it is a
Hello,
Is it possible to compile OpenSSL shared libraries with custom names on
Linux/ Unix platforms to avoid conflicts with installed OpenSSL libraries?
I have tried to modify the SHLIB_EXT in Configure script but it is
not working. I am sure it is a common problem and someone in this group can
h
