Hi,

In Debian, cURL already ships with libraries that use OpenSSL, GnuTLS
and NSS. There is a merge request on Salsa which will also ship a
version with wolfSSL:

https://salsa.debian.org/debian/curl/merge_requests/6

The creator of cURL joined the wolfSSL team earlier this year:

https://www.prweb.com/releases/wolfssl_announces_integration_with_curl_daniel_stenberg_founder_and_chief_architect_of_curl_to_join_wolfssl/prweb16070779.htm

In one peculiar case, the package icecast2 may use wolfSSL in the
future, but in addition depends on libcurlX. It would be more
consistent for icecast2 to use wolfSSL in both parts of its software.

Kind regards,
Felix Lechner

Thanks for raising this, and the patch.

Adding a new flavour of curl is a bit costly as each one of them adds
around 15m of build time (on good machines). Most of the build time is
spent running the unit tests, which are quite complete, so I often build it
with the nocheck profile, nonetheless the impact is still there as we have
to run the tests at some point.

I have to be able to justify the extra maintenance cost for this change, so
please send other usecases you're familiar with here.

I won't ask for much, but it seems that currently wolfssl usage within
Debian is low as per popcorn [0]. Of course popcon is not very reliable as
base for such things so as I mentioned please let me know of more data you
might have (also I understand there might be other software who will only
migrate to wolfssl once curls provides this).

Does this make sense to you?

[0] https://qa.debian.org/popcon.php?package=wolfssl

Cheers,

Please read #1023697 on why you should not enable a wolfSSL flavour.
Also, icecast2 has dropped its wolfssl dependency.