Closed der-eismann closed 8 months ago
Yes, curl currently targets rustls-ffi 0.11. Most likely it is on us to submit a PR to curl to account for the breaking changes we made in 0.12.
Ah, I wasn't sure how stable/compatible the APIs are. So should I close this or how do you want to proceed?
Ah, I wasn't sure how stable/compatible the APIs are
We're following the conventional Cargo semver guidelines where:
releases starting with “0.y.z” can treat changes in “y” as a major release, and “z” as a minor release.
It's best to assume each increment of the "y" component is a major release that will be incompatible with previous versions without code changes. Similarly, there's no guarantee of ABI stability across releases at this time.
So should I close this or how do you want to proceed?
Perhaps an issue on the curl repo to track an update to the latest Rustls is the best path forward?
I agree with Ctz that it's likely one of the Rustls maintainers (or a motivated 3rd party :-)) would need to do the work. For me personally I find it time intensive to spin up on a large C project's build system/codebase and so while I'm interested I haven't been able to find the time.
Alright, opened https://github.com/curl/curl/issues/12737. Hopefully someone finds the time soon :slightly_smiling_face:
Thanks! I'll close this issue so we can coordinate in the repo where the work needs to be done.
And BTW, rustls.h
still have references to this symbol rustls_client_config_builder_load_roots_from_file()
in it's comments and elsewhere:
https://github.com/search?q=repo%3Arustls%2Frustls-ffi%20rustls_client_config_builder_load_roots_from_file&type=code
Hi everyone, please let me know if this needs to be addressed in curl instead, but since building curl worked fine with 0.11.0 and failed with 0.12.0, I felt this is the correct place.
So I built rustls-ffi with
make PROFILE=release
& rust 1.74.0. Afterwards I tried to build curl 8.5.0 with clang 16 andand as a result I got the following errors:
Does curl need to update its rustls support? Or is it an issue with this library? Thanks!