[strongSwan] Which version of openssl to use with strongswan

[Peter Hsiang]

Hi Tobias,


Thanks.  The version of boringssl on strongswan.org has not been updated for about the same amount of time as the openssl on strongswan.org.

Would Google also reject app compiled with this version of boringssl when uploading to Play?


Building with the Android's build tools (Android repo, and not just NDK), the system's boringssl library is built and the object files for 'libcrypto' goes to the common output directory path:

./obj/SHARED_LIBRARIES/libcrypto_intermediates

Even for static lib build, the non-system copy of any library sharing the same lib name would normally write to the same output path.  Perhaps there is a different build setup without the visibility to the system's copy of libcrytpo so there is no issue of paths collision?


Thanks,

Peter

________________________________
From: Tobias Brunner <tobias at strongswan.org>
Sent: Wednesday, October 24, 2018 12:23:13 AM
To: Peter Hsiang; users at lists.strongswan.org
Subject: Re: [strongSwan] Which version of openssl to use with strongswan

Hi Peter,

> Do we have porting guidelines for integrating strongswan with boringssl for Android P?

Nope.  You shouldn't use the system's libraries from an app anyway.

> I see there is an older version of boringssl https://git.strongswan.org/?p=android-ndk-boringssl.git;a=log

That's exactly what I was referring you to.

> Would this work on Android P, and would it co-exist with the copy already in Android P (sharing the same libcrypto_static.a object files name space)?

The openssl plugin (or rather libstrongswan) links that version
statically, which doesn't seems to conflict with anything the Java part
does.

Regards,
Tobias

-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.strongswan.org/pipermail/users/attachments/20181025/1f17304e/attachment.html>