3 ms·
This is a very interesting discussion between two practitioners that I have tremendous respect for. To me the discussion highlights one interesting point: the
by wglb 13y ago
This is a very interesting discussion between two practitioners that I have tremendous respect for.
To me the discussion highlights one interesting point: the provability of programs. In particular, Colin says I recommend a more modern approach to cryptography — which means studying the theory and designing systems which you can prove are secure.
Now, I remember back in the days of structured programming, and we were all reading Dijkstra and thinking about proving programs. We concluded that it was a pretty expensive to do so. In all my decades of programming, I haven't made a serious attempt to do so. The best I have done is to (sometimes) write programs that are hopefully provable.
The possibility of writing provable programs to me is confounded by the work done by John Regehr, who seems to be the current champion of fuzzing compilers. His techniques find legions of bugs in compilers, including 17 errors in one research compiler that is _proved correct_.
Nonetheless, my question for Colin is how many programmers do you feel are capable of proving programs correct, be they compilers or cryptography libraries? For those of you who haven't given it a shot, take a look at some of the links on the side of Colin's blog post, the "Software Development Final Exam". Not very many of us did very well with that. (My feeble excuse is that there weren't any computer science departments when I went to Engineering School.)
I guess that Colin would agree that anyone who does not do well on those exams might not do well in writing and proving programs correct.
And on the other hand, Thomas explodes stuff that is written by a range of programmers covering the whole spectrum of talent. He sees on a day-by-day basis of the result of confident, talented programmers when subjected to excruciating punishment.
I do enjoy the discussion between these two.
- wglb 13y agoUh, the programs are subject to excruciating punishment, not the programmers. Just to clarify.
- nknighthb 13y agoI'm reminded of a talk by a guy who ran a penetration testing team (I think in Israel?) which was hired by a bank on a highly permissive contract. It led to them trying to physically rob the bank just because they could. (Spoiler: It didn't go well.) Unfortunately, I don't know many programmers who would take kindly to rubber hose pentesting.
- andrewaylett 13y agoThis? https://www.youtube.com/watch?v=RJVHTQSvUIo https://www.youtube.com/watch?v=RJVHTQSvUIo
- TeMPOraL 13y agoOne of the problems with proving programs is that proofs tend to get as complex as the code they're proving, at which point one has to be wary of bugs in proofs. One (possibly only) way around this would be to prove an automated proof checker and use it to prove better automated proof checkers, and so on, up until you get a tool you trust that can reliably make proofs for you.