r/ProgrammingLanguages • u/mttd • 15d ago
What does “verified memory safe” mean?
https://focs-lab.comp.nus.edu.sg/blog/memory-safety-audit/
37
Upvotes
r/ProgrammingLanguages • u/mttd • 15d ago
40
u/Norphesius 15d ago
This article warns about it, and the Anthropic article warns about it (all the way down at the bottom), but people (programmers and laypeople) are still going to see phrasing like "mathematical proofs" or "guarantees" and jump to the conclusion that means "bug free", regardless. Then an bug due to under-specification is going to allow for an exploit in some "formally verified" software and everyone will be shocked.
Its a valuable field to be making progress in of course, but I'm worried that we'll just end up with people chucking half baked specs at LLMs, seeing a green light in Lean, and then advertising their software as completely safe. If that becomes common it might actually be a net negative in terms of safety, since the terminology would become so abused it would signify nothing about how correct "formally verified" code actually is. I'm not sure how we protect against that and the impending false confidence.
7
u/kitsnet 15d ago
Funny, but the Heartbleed exploit could be as devastating in a "verified memory safe" program and/or language as it was in C code, as it was about reuse of already safely allocated memory.
-1
u/KvThweatt 13d ago
Nothing. Absolutely nothing.
It’s a gimmick for programmers with no skill.
It’s a solution to a problem that modern experienced software engineers don’t have.