Skip to main content

in reply to daniel:// stenberg://

Apple considers their Secure Transport API as "legacy", being stuck at 1.2 (and not getting 1.3) developer.apple.com/documentat…
in reply to local area ian

@ecn I am aware. I think my bigger concern is that we have a lot of users using this and I'm not sure all of them have any easy/proper alternatives...
in reply to daniel:// stenberg://

yeah :/ TLS Inspector uses it but I'll probably switch it to using OpenSSL instead going forward.

The replacement, Network Framework, is vastly different and mostly asynchronous. Kinda a pain to work with really.

in reply to local area ian

@ecn Network Framework sounds quirky indeed and I imagine it might take some unpleasant hacks to use that. I can imagine we'll see some efforts in that direction in the future.
in reply to daniel:// stenberg://

yes please drop those libraries - abandonware is not a good idea for software
Unknown parent

daniel:// stenberg://
@BradRubenstein we don't break existing functionality so upgrading curl is rarely a technical issue, just some lame problems with users getting stuck on old distros and running old systems.
Unknown parent

daniel:// stenberg://
@BradRubenstein we have dropped support for several 3rd party libs in the past. We have changed defaults so that for example SSLv2 and SSLv3 can't be used etc.
in reply to daniel:// stenberg://

I'm using libcurl on Riscos. Would this cause the riscos port to stop working?
in reply to Elias Mårtenson

@loke are you saying that you only have one of those TLS libraries to select from on Riscos?
in reply to daniel:// stenberg://

Oh wait, you're right. Libcurl on riscos links with openssl, so that should be fine.
in reply to Elias Mårtenson

@loke I am also proposing a suitable date far enough in the future to allow adaption time
Unknown parent

daniel:// stenberg://
@BradRubenstein curl currently supports twelve different TLS libraries. This discussion concerns three of them. Which maybe by the time next year might no longer be all three...
in reply to daniel:// stenberg://

well, as an embedded (and MS-DOS) developer I would plead to keep it (mbedTLS does not support it)...