Hello,
So as you may have seen (at least the users knows):
- OpenSSL version is absolutely outdated and no longer maintained.
So I wish to know what is the best practice ?
Is there any work or incoming patch for this issue ?
Thanks.
Epic is likely sticking with this outdated version of OpenSSL for compatibility reasons. The version of OpenSSL that comes with the engine is cross-platform compatible and continues to support older versions of these platforms, such as older Android devices.
If you need an OpenSSL version greater then 1.1.1t, you can download its source code, compile its static libraries for your target platforms and make a dependency entry in the build.cs files.
I am already using the source code directly.
- option : compile its static libraries for your target platforms and make a dependency entry in the build.cs files.
Yeah but from what I understand it’s very intricate and complex ? Especially deep inside ?
Well, one of my own plugins also uses OpenSSL, but I actually reverted back to v1.1.1t to simplify the plugins build process for other users. So the build scripts that I used for OpenSSL 3.6.3 are already deleted.
If I remember correctly, you can also download pre-built versions for Windows and Mac.
Yeah but no, prebuilt ones lacked some functions to build the game, I had no other choice but to compile from sources.
What I would like to know is : did they take that into account ? Because nowadays with AI it’s an additive stress thing.