Re:How can C Programs be so Reliable?
by haberman on Thursday September 22, 2011 @01:33PM
(#3026874)
> There's a pretty famous Mark Dowd Sendmail vulnerability that relies almost entirely on (only- incidentally- sent-) signal timing that I like to use as an example here
Would love to see a reference to this.
The unwillingness to cut and paste "mark dowd sendmail" into google for something you would "love to see" is amusingly typical of lots of the comments on this thread. It's the first result BTW
I like the second result better than the first, for what it's worth. ;)
But come on. While let-me-Google-that-for-you requests are annoying, they are in toto less toxic to threads than comments like yours; at least the lame question generates a factual answer.
Re:How can C Programs be so Reliable?
by haberman on Saturday September 24, 2011 @12:13AM
(#3032488)
FWIW I Googled for "mark dowd signal timing sendmail vulnerability" which led me to http://lwn.net/Articles/176596/ which didn't look like the right vulnerability and gave me the impression that Mark Dowd does a lot of vulnerability research -- it seemed that finding the exact vulnerability tptacek was talking about might be more complicated than just asking him directly.
Re:How can C Programs be so Reliable?
by coliveira on Thursday September 22, 2011 @02:26PM
(#3027118)
> buttoning down a C runtime environment so you can be rely on the assumptions behind those abstractions is a chore.
may be hard, but not more difficult than creating the run time for any other language such as Java or Python -- and they are all written in C.
The problem is, your code will appear to work fine even if you don't complete the chore. It isn't until your program blows up that it'll even occur to you that there was more work to be done.