> On 16 Aug 2021, at 11:33 am, Goetzke, Arnold (A.P.) wrote:
>
> Thanks for that Viktor - I'll see if the shlib_variant is an option.
Note that setting "shlib_variant" is something the vendor has to set
when building the bundled OpenSSL libraries. The Configurations/README
file documents this a
Thanks for that Viktor - I'll see if the shlib_variant is an option.
From: openssl-users on behalf of Viktor
Dukhovni
Sent: Monday, August 16, 2021 11:29 AM
To: openssl-users@openssl.org
Subject: Re: One iOS App - 2 OpenSSL libraries.
WARNING: This me
On Mon, Aug 16, 2021 at 12:57:54PM +, Goetzke, Arnold (A.P.) wrote:
> We have a large application, and two vendors are using the OpenSSL
> library in their project. However, only one of the projects encrypts
> data successfully when joined in our application
>
> Is this a known limitation?
There shouldn't be a limitation. Although if two different versions of
OpenSSL are being used, it is possible that they could interact together
in odd ways.
OpenSSL will automatically use assembly implementations of algorithms
unless:
* the "no-asm" option is specified at configuration tim
Hi -
We have a large application, and two vendors are using the OpenSSL library in
their project. However, only one of the projects encrypts data successfully
when joined in our application
Is this a known limitation?
Also, is there a way to enable Bit-Code for iOS when compiling? I don't se
