Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: I finally could build curl on Windows with SSL support - will you update the docs?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Fri, 15 Apr 2022 11:37:58 +0200 (CEST)
On Wed, 13 Apr 2022, Julien Matthey via curl-library wrote:
> Trying to link against SSL boderline made my head explode so... I think it
> should be documented that on Windows platforms, users should use
> CURL_USE_SCHANNE, or have CMAKE use this option by default.
I disagree. We support a wide variety of TLS backends for libcurl and most of
them work for Windows too. Sure you can chose to go with Schannel if you want
to, but I don't think we whould or need to push users that way rather than all
the other choices.
We should rather work on improving the documentation to make it easier to
build with any of them.
> Also, at first, when I built curl with *no* SSL backend, $curl -V would still
> print:
>
>> curl 7.79.1 (Windows) libcurl/7.79.1 Schannel
>
> which means the curl tool executable uses the Schannel SSL backend no matter
> what, and indeed something like:
I don't believe this. When it says 'Schannel' there, it was built with TLS
support and with Schannel specifically. The code shows this.
Date: Fri, 15 Apr 2022 11:37:58 +0200 (CEST)
On Wed, 13 Apr 2022, Julien Matthey via curl-library wrote:
> Trying to link against SSL boderline made my head explode so... I think it
> should be documented that on Windows platforms, users should use
> CURL_USE_SCHANNE, or have CMAKE use this option by default.
I disagree. We support a wide variety of TLS backends for libcurl and most of
them work for Windows too. Sure you can chose to go with Schannel if you want
to, but I don't think we whould or need to push users that way rather than all
the other choices.
We should rather work on improving the documentation to make it easier to
build with any of them.
> Also, at first, when I built curl with *no* SSL backend, $curl -V would still
> print:
>
>> curl 7.79.1 (Windows) libcurl/7.79.1 Schannel
>
> which means the curl tool executable uses the Schannel SSL backend no matter
> what, and indeed something like:
I don't believe this. When it says 'Schannel' there, it was built with TLS
support and with Schannel specifically. The code shows this.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2022-04-15