@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.
@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.
@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.
@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...
quite possibly an ian
in reply to daniel:// stenberg:// • • •Secure Transport | Apple Developer Documentation
Apple Developer Documentationdaniel:// stenberg://
in reply to quite possibly an ian • • •quite possibly an ian
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.
daniel:// stenberg://
in reply to quite possibly an ian • • •Bálint Szilakszi
in reply to daniel:// stenberg:// • • •mc.fly
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
Unknown parent • • •daniel:// stenberg://
Unknown parent • • •Elias Mårtenson
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Elias Mårtenson • • •Elias Mårtenson
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Elias Mårtenson • • •daniel:// stenberg://
Unknown parent • • •daniel:// stenberg://
Unknown parent • • •SuperIlu
in reply to daniel:// stenberg:// • • •