On Fri, 19 Feb 2021, Michał Antoniak wrote:
this looks like an area for improvement in the mbedTLS backend as I don't
think there's any good reason for this struct to be this big.
I also think the mbedtls team can come up with a better solution.
The mbedTLS team has not been involved at all
pt., 19 lut 2021 o 13:54 Daniel Stenberg napisał(a):
> First, they're not "encryption libraries", they're TLS libraries. They do
> much
> more than just encryption.
Yes, I mean TLS libraries. Sorry for this inaccuracy.
Then: this looks like an area for improvement in the mbedTLS backend as I
>
On Fri, 19 Feb 2021, Michał Antoniak wrote:
In our project we use the mbedtls library. After our optimizations, the
ssl_backend_data structure is 1828 bytes in size. Unfortunately, I don't
know about other encryption libraries.
First, they're not "encryption libraries", they're TLS libraries.
In our project we use the mbedtls library. After our optimizations, the
ssl_backend_data structure is 1828 bytes in size. Unfortunately, I don't
know about other encryption libraries.
czw., 18 lut 2021 o 10:59 Daniel Stenberg napisał(a):
> On Thu, 18 Feb 2021, Michał Antoniak via curl-library w
On Thu, 18 Feb 2021, Michał Antoniak via curl-library wrote:
https://github.com/curl/curl/blob/e72270236cf7606069907f91e55e02c5ed54df4a/lib/url.c#L1640
Is it intended to allocate memory for ssl backend data 4 times?
Yes. libcurl might use two TLS connections for host and the logic is mostly
