Skip to main content


In #curl, we are back discussing deprecating TLS libraries without 1.3 support: github.com/curl/curl/pull/1354…
#curl

Seirdy reshared this.

in reply to daniel:// stenberg://

sorry, I‘m abroad and have no access to my GitHub account RN: you mention only bearSSL and the Apple library in the linked ticket. Wasn’t mbedTLS on the drop-list as well?
Or does mbedTLS 3.x support TLSv1.3 now? I’ve yet to look into 3.x as I’m using 2.28.x in several projects and AFAIK that does not support TLSv1.3...
in reply to SuperIlu

@dec_hl this PR is about to bring 1.3 support to mbedTLS: github.com/curl/curl/pull/1353…
in reply to daniel:// stenberg://

@dec_hl The version of mBedTLS with 1.3 support is huge. The focus seems to have shifted from Trusted Firmware, where you're running a small codebase at boot time, not tiny embedded systems.

We moved from mBedTLS to BearSSL because recent mBedTLS's new code size is larger than the total amount of RAM on the devices I care about.

Curl is also larger than I'd want to run on these devices (much less than 1 MiB of RAM in total), so that shouldn't be a problem.

I would love to see a from-scratch tiny QUIC library for embedded devices so that we could remove TCP support entirely.

in reply to David Chisnall

with tiny-curl I aim to provide a HTTPS GET-centric libcurl build at around a 100K foot-print (on a 32 bit arch) - which is possible with wolfSSL (at least)
This entry was edited (6 months ago)