▲ | What is memory safety and why does it matter?(memorysafety.org) | |||||||
7 points by fuzztester a day ago | 5 comments | ||||||||
▲ | rurban 8 hours ago | parent | next [-] | |||||||
> Consider Rust. What about advertising actual memory safe languages instead. https://github.com/Speykious/cve-rs | ||||||||
▲ | fuzztester a day ago | parent | prev | next [-] | |||||||
https://www.abetterinternet.org/ | ||||||||
▲ | fuzztester a day ago | parent | prev | next [-] | |||||||
Saw this via a chain of links starting from the Let's Encrypt site. | ||||||||
▲ | Panzerschrek 20 hours ago | parent | prev [-] | |||||||
Yet another article misleadingly treating C and C++ both as memory-unsafe languages. But there is a huge difference between them. Modern C++ code written according to strict standards (like C++ core guidelines) is much less vulnerable in comparison to C code or old-style C++ code. So in practice it may be enough to write in C++ a modern way to avoid vulnerabilities or at least greatly minimize them. Adopting a new memory-safe language may be much more harder, especially in large existing codebases. And strictly speaking Rust isn't memory-safe, since it allows to shot the leg via unsafe blocks. | ||||||||
|