Practical Memory Safety

Memory safety is a hot topic that some find confusing and controversial. However, it's essential to understand that memory safety is about having clear and easy-to-follow rules for handling memory. In this post, we'll explore the concept of memory safety and why it matters.

Consider this C code example. It allocates memory for a User struct and copies a string from the first command-line argument. But what happens when the input string is longer than 8 characters? The `strcpy` function will happily overwrite memory that you own, potentially allowing unauthorized access or behavior. Although this code is not technically "exploitable," it's a clear example of a memory safety issue.

The concept of memory safety varies between different programming languages and paradigms. For instance, Fil-C defines memory safety as having runtime checks to prevent exploitable memory safety errors. In contrast, a language like Yolo-Zig may allow such unsafe operations but could still be safer than Yolo-C.

So, what is memory safety? A practical definition is that memory-safe code should have intuitive and easy-to-follow rules for memory handling, unless there's a clear indication that rules are different. This definition acknowledges that memory safety is important for ensuring that safe operations on memory match our general expectations while keeping the rules simple and enforceable.

However, even with these rules, there may still be unmarked and unchecked memory footguns that require user awareness and vigilance. The goal of memory safety is to reduce the overall subtlety and complexity of memory handling, allowing developers to focus on their primary tasks without being burdened by excessive technical details.

In conclusion, memory safety is essential for creating reliable and secure software. By establishing clear and enforceable rules, we can minimize the risk of memory-related issues and provide a better development experience. Ultimately, memory safety is about having less subtlety overall, so that developers can concentrate on the aspects of their work that matter most.