News for hackers. Stuff that matters.
Re:How Did Software Get So Reliable Without Proof? (1996) [pdf] by lmm on Wednesday March 16, 2016 @05:28AM (#11296017)
Most of the security vulnerabilities involve C undefined behaviour. Any proven-correct program necessarily won't invoke undefined behaviour.

(We could also have used memory-safe languages)

Re:How Did Software Get So Reliable Without Proof? (1996) [pdf] by gefh on Wednesday March 16, 2016 @12:42PM (#11298665)
Many, but I'm not sure most. However they nearly all involve someone (be it the language designer, compiler writer or application writer) not thinking about all the malicious possibilities of the code in question. Because that's not the problem they're trying to solve right now, and they're only human. And I only use security vulnerabilities as an example - the next thing we're all not thinking about might be power consumption, or creating AI paradoxes, or whatever. But we're definitely not thinking about it, and no-ones going to be proving it.
Re:How Did Software Get So Reliable Without Proof? (1996) [pdf] by lmm on Thursday March 17, 2016 @07:52AM (#11303767)
> And I only use security vulnerabilities as an example - the next thing we're all not thinking about might be power consumption, or creating AI paradoxes, or whatever. But we're definitely not thinking about it, and no-ones going to be proving it.

I don't think you have to be thinking about it. Every time some new class of vulnerabilities has arisen, e.g. SQL injection, it just hasn't affected well-formed programs written with good tools, and certainly not verified programs. Correct programs just don't have these problems, as a side effect of being correct.

Re:How Did Software Get So Reliable Without Proof? (1996) [pdf] by gefh on Wednesday March 16, 2016 @12:46PM (#11298693)
Also there are probably zero non-toy programs out there that don't have any undefined behavior in them :)
Re:How Did Software Get So Reliable Without Proof? (1996) [pdf] by raverbashing on Wednesday March 16, 2016 @06:13AM (#11296163)
Correct, but "undefined behaviour" sometimes mean "defined by machine"

I mean, pretty much the same way as int or size_t has a machine type size dependency

Re:How Did Software Get So Reliable Without Proof? (1996) [pdf] by lmm on Wednesday March 16, 2016 @06:25AM (#11296205)
Not true in theory or in practice. "Undefined behaviour" has a specific meaning in terms of the C standard, distinct from "implementation-defined behaviour" like the size of int or size_t. And in practice, writing beyond the bounds of an array almost always leads to arbitrary code execution (remote in the case of a networked program), double free almost always leads to arbitrary code execution, signed integer overflow on newer compilers sometimes leads to arbitrary code execution, ...