Google Play - how do you deal with outdated OpenSSL issue?

:information_source: Attention Topic was automatically imported from the old Question2Answer platform.
:bust_in_silhouette: Asked By lukas
:warning: Old Version Published before Godot 3 was released.

Google announced:

Please migrate your app(s) to OpenSSL 1.02f/1.01r or higher as soon as possible and increment the version number of the upgraded APK. Beginning July 11, 2016, Google Play will block publishing of any new apps or updates that use older versions of OpenSSL.

It also affects games made in Godot since it uses old version of OpenSSL.

I know that we can compile Android export template with flag openssl=no. But can it somehow damage functionality of a game?
To what exactly (in which functions or nodes) is OpenSLL used in Godot?

See this issue.

dragoon | 2016-04-05 04:20

:bust_in_silhouette: Reply From: Akien

For now the best solution is to build templates with openssl=no indeed, unless you really need OpenSSL support. AFAIK, OpenSSL is used for HTTPS support, and maybe its libcrypto is used for some encryption tasks, though I’m not sure.

Will it be a problem if we use third party ad libraries or Google iaps?
Being open source, there should be a way to overcome this.

vinod | 2016-04-05 11:40

No idea about Google IAPs or other monetization libraries. I guess the best way to know is to try it.

And yes of course the better solution is to update the bundled OpenSSL source, which can be done by anyone, see Builtin OpenSSL is outdated · Issue #2780 · godotengine/godot · GitHub
It’s not so trivial though, but should be doable by someone with some spare time.

Akien | 2016-04-05 11:43