in reply to daniel:// stenberg://

I am curious about programming "discipline" to avoid things like stack overflows, invalid or null pointer dereferences, etc. Does curl use fixed array sizes, especially for arrays allocated on the stack? Is there bounds checking, and do lint-tools check bounds at compile time? Are freed pointers assigned to NULL to prevent referencing deallocated memory? There are tradeoffs between the Rust-style borrow checker requirements, and the flexibility of manual data structure management.
in reply to Daniel Marks

@profdc9 we do try to make it hard to do wrong, daniel.haxx.se/blog/2023/12/13… - but recall that 60% of the curl security problems were *not* C problems.
Unknown parent

mastodon - Link to source

daniel:// stenberg://

@kurtseifried The main problem in my view is that virtually nobody cares about the CWE. No one ever complains about it or asks for it to get change etc. We basically put a finger in the air during 20 seconds when writing the advisory, search around all the available ones and then go with the one we think is the least bad one. And we never go back to reconsider and no one propose anything else.

So they are all fairly arbitrary but "decent" because we try to pick an accurate one.