2 ms·
You'd be foolish to sit under the piano if only some piece of software is verified, and not the entire operating system, and the silicon. And not just the corre
by kazinator 5y ago
You'd be foolish to sit under the piano if only some piece of software is verified, and not the entire operating system, and the silicon. And not just the correctness of blueprint of the silicon, but the freedom of manufacturing defects of that exact build of the silicon, and all the hardware around it: every DRAM memory cell, every capacitor. That still leaves the possibility that a bit is flipped due to silicon being struck by radiation. Consumer-grade hardware is quite susceptible to random errors caused by cosmic rays.
All verification makes assumption about some lower layer that is not itself verified.
For instance, you can't deduce the issues uncovered by Meltdown and Spectre from the semantics of the x86 instruction set architecture; so if you use that alone, you can falsely prove that x86 programs don't have security problems.
Rationally speaking, you shouldn't take any risk, however small, where there is no benefit. You wouldn't risk $1000 if the expected value from the entire risky event $900. If you're putting your life on the line, there has to be something in it other than convincing people that you really believe in something being correct.
Consider this: people have died for the sake of showing that their belief (e.g. religious) is correct! For instance, set themselves on fire or blown themselves up, or suffered as martyrs all the way to death. Just because some programmer put himself under the piano while his code was being fuzzed doesn't mean that it's correct, just that he or she is reckless and has a fanatical belief in the work. (If the programmer is reckless, I'm disinclined to believe in his or her code.)