You are not logged in.
Pages: 1
https://www.abetterinternet.org/post/memory-safe-curl/
Curl has got a new backend for TLS written in rust. Apparently we can stick with the C-based backend with a configuration option, which we might need to do, if the upstream project doesn't take this route. Or perhqps rust isn't such problem any more, and we can make use of the newer backend.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
If we get whole Linux rewritten in Rust, we might end up mainly in a build slave problem, as Rust is much much more powrehungry than C or C++.
Otherwise we must bootstrap i486 Rust then, really, that's the only issue in the immanent future..
Offline
as nice, as it sounds to have memory-safe rustish backends in curl, as bad is it for all other backends, because they'll be less thoroughly tested ...
Offline
It seems slightly surprising to me the the C backend reportedly had so many corner cases that end up in undefined behaviour. I'm a fairly heavy user of curl directly, using it at least 100 times a week, and I've never seen it go weird on me.
But if we can get i486 rust bootstrapped, and that's all of the rusts up to date then we can use the perhaps mainstream backend (unless everyone sticks with the C backend).
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Pages: 1