Related to coronalabs/corona#534.

The current version of OpenSSL has many vulnerabilities and needs to be updated. And according to OpenSSL 1.1.1 End of Life, I have two questions:

About OpenSSL version:

1. Due to the outdated 1.0.2 series, the latest public version 1.0.2u still has many vulnerabilities (our colleagues have tried to update), so it is not recommended.
2. The 1.1.1 series will also stop public maintenance in September this year. Compared with take the 3.x series, the advantage is that compatibility issues may be relatively low, and there is less content to deal with. However, according to the recommendation, another upgrade will be required in half a year.
3. The 3.0 series is LTS and will be supported until September 2026, while the 3.1 series is not LTS and will be supported until March 2025.

About Apple Xcode version (related to binary architectures support):

1. Xcode 14, according to Apple submit - Build with Xcode 14.1, starting April 2023, all iOS and iPadOS apps submitted to the App Store must be built with Xcode 14.1 and the iOS 16.1 SDK (or later, AFAIK), which should already be in effect. However, Xcode 14 removed the 32-bit SDKs, and as a result, this plugin will not support game developers who do not need to be on the App Store.
2. Xcode 13 has better compatibility, but may not be necessary under Apple's policies?

IMO, the first step should be try upgrading to the OpenSSL 3.0 series. If there are compatibility issues with third-party libraries, then support for the latest version of 1.1.1 can be considered as a backup. For Xcode, I suggest using Xcode 14 for compilation.

Currently, we will follow the above approach to make an attempt and submit a PR at the appropriate time.

What do you think?

I'm running a project with plugin_openssl on windows simulator 3696.
But I got this error: