Compilation warnings when building for iOS min version 13 #11098
I did this
Compiling curl for iOS and min versions iOS 13
configure: Configured to build curl/libcurl:
I expected the following
No warnings in the compilation.
Compiling version 8.0.1 (probably happens with previous versions too)
Chip: Apple M1 Max
The text was updated successfully, but these errors were encountered:
I'm not very fluent in macOS specifics, but "Use Network.framework." seems to imply that a rather major effort would be necessary to address these in other ways than just inhibiting the warning messages. I don't see this happening anytime soon.
Indeed, it seems Apple deprecated SecureTransport as-is:
...I stand corrected with "temporary"!
For the warnings in md4.c and md5.c, we don't use the system functions anymore for recent macOS since 2998749 because of the possible warnings-as-errors. We could do the same for iOS.
Also, we can probably include MD4 support only if
For SecureTransport, the only actionable warning seems to be this one:
If you don't want functions deprecated by Apple to be used, don't choose a framework deprecated by Apple as an SSL backend.
Turns out the macOS case I mentioned is not related to SecureTransport, but to
The md4/md5 part should be addressed by #11102.
I cannot fix the
Thank you for checking this and for the great efforts 🙌 .
Nice to see that you addressed "This function is cryptographically broken and should not be used in security contexts" warnings 💪.
I understand. I can use Secure Transport as SSL backend (or other SSL supported library: OpenSSL, GnuTLS, NSS, wolfSSL, mbedTLS, Schannel) but I can't use "Netwrok.Framework" because it is not supported as SSL backend library and it is something not planned to add in a near future.