Hi Praveen,
I guess you are integrating fips compliant. I have a
question that how to call FIPS_mode_set(1), in our code as I am new to
ANDROID NDK. I have not seen any question regarding this , can you please
help me in this regard.
Thanks,
kondlada
On Tue, Sep 25, 2012 at 8:33 PM, Thakur, Praveen Kumar <
praveenkumar_tha...@bmc.com> wrote:
> I don’t see any issue if .so files extension is 1.0.0. However, I wanted
> to confirm that is this a defect with 1.0.1 release? Or am I missing
> something.****
>
> Thanks,****
>
> Praveen****
>
> *From:* owner-openssl-us...@openssl.org [mailto:
> owner-openssl-us...@openssl.org] *On Behalf Of *karthik kondlada
> *Sent:* Tuesday, September 25, 2012 7:09 PM
> *To:* openssl-users@openssl.org
> *Subject:* Re: libs version are 1.0.0 after compiling openssl 1.0.1c****
>
> ** **
>
> Hi Praveen,
>
> In linux you would expect extension to so files as such
> you have received. I think when we use system.loadlibrary method will get
> errors so have to execute using system.load method.
>
> Regards,
> kondlada****
>
> On Tue, Sep 25, 2012 at 10:23 AM, Thakur, Praveen Kumar <
> praveenkumar_tha...@bmc.com> wrote:****
>
> Hi,****
>
> ****
>
> I have compiled OpenSSL 1.0.1c. After compilation libs which are generated
> contains version number as 1.0.0.****
>
> ****
>
> For example: libssl.so.1.0.0, libcrypto.so.1.0.0****
>
> ****
>
> Is this a defect with OpenSSL 1.0.1c? Ideally library names should have
> been libssl.so.1.0.1, libcrypto.so.1.0.1****
>
> ****
>
> Thanks,****
>
> Praveen****
>
> ****
>
> ** **
>
