10 ms·
ah yes, tried and tested C/C++ which has tons of memory-safety bugs leading to RCEs and more.
by Ar-Curunir 5y ago
ah yes, tried and tested C/C++ which has tons of memory-safety bugs leading to RCEs and more.
- exdsq 5y agoBut you can avoid these by following best practices and using tools to find them. These are known knowns and there are solutions. The issue with Rust and others is that there are so many unknown unknowns, because it hasn't had the same number of hours of development time and usage. Have you ever used a language like Haskell in a formal verification environment? You still get memory issues but there are far less tools to tackle them.
- Ar-Curunir 5y agoSorry, but what? Every big C/C++ project is regularly plagued by memory-safety issues. This is a blog post from Chrome where the majority of bugs are memory-safety bugs: https://chromereleases.googleblog.com/2022/03/stable-channel-update-for-desktop_29.html https://chromereleases.googleblog.com/2022/03/stable-channel... This is a project with world-class resources for enforcing memory safety, and yet they regularly encounter this class of bugs. C and C++ do not provide sufficient tools to prevent memory safety, and this has been demonstrated across basically every project they're used in.