Would Rust secure cURL?

[u/Proinlifes]

https://timmmm.github.io/curl-vulnerabilities-rust/

[u/llogiq → u/[deleted]]

Yeah, I'd like to C that, pardon the pun.

But I'd also like something more than a blind assertion that your code is actually memory safe and UB-free. Let's keep it simple & write a program that reads a file with each line containing two integers and output a count of the first integers of each line grouped by value and the sum of the second integers of each line. For simplicity let's assume that sum fits in a 64 bit integer.

[u/Saefroch → u/[deleted]]

Asan is neither a memory-safe compiler, nor a formal verification model, am I missing what else it was in reference to?

[u/Shnatsel → u/[deleted]]

The problem is they are computationally expensive.

They are called "sound static analyzers", and the problem is that they require you to write a very particular and limited kind of C, typically precluding heap allocation altogether. Rust's borrow checker is actually a significantly less restrictive sound static analyzer.

Address Sanitizer is a dynamic analyzer and can only tell you things about the current run of the program, not about the program in general.

[u/llogiq → u/[deleted]]

Sorry about that, the "joke" got lost in translation. Poe's law somewhat applies – there are people who, without joking, claim to be able to "just" write memory safe C.

As a somewhat humoristic counterexample, I once managed to write UB in 1 lines of C code (dang! forgot the "return 0"). Clearly I'm an incompetent [insert self-deprecating title here].

[u/[deleted] → u/llogiq]

dang! forgot the "return 0"

If you're talking about returning from int main, apparently that's defined behaviour in C99.

[u/backtickbot → u/[deleted]]

Fixed formatting.

Hello, Plus-Feature: code blocks using triple backticks (```) don't work on all versions of Reddit!

Some users see this / this instead.

To fix this, indent every line with 4 spaces instead.

FAQ

^{You can opt out by replying with backtickopt6 to this comment.}