Researchers have found memory corruption flaws in both Daniel J. Bernstein and Wietse Venema's code. You want to try this "de-myth-ification" thing again?
Researchers have found memory corruption flaws in both Daniel J. Bernstein and Wietse Venema's code. You want to try this "de-myth-ification" thing again?
It is a simple rule. Never trust user input, the issue has been known for decades and everybody should be aware of it by now.
If you aren't deliberately trying to miss the point, TFA claimed "only idiots make buffer overflow error" and the OP is implying it's not just the idiots, but very smart people(look up the names) who make buffer overflow errors as well.
> It is a simple rule. Never trust user input, the issue has been known for decades and everybody should be aware of it by now.
It's a simple rule. Don't write buggy code. The issue has been known for decades and everybody should be aware of it by now.
/s
I am trying to find the buffer overflow in DJB's code. I am more interested in the fact if it was a simple error(give too long an input and it goes kaboom), or a complicated one. My intuition is it is the complicated kind. DJB is known to actively use his own implementation of stdlib and strings which are coded from scratch to be secure than the standard counterparts.
Here's a chance for you to improve your standpoint; I'd recommend taking two minutes aside, typing both names into Google and reading a bit about both people first. You might learn something ;)
If you get owned by something that isn't well known, by a bug in the CPU, by a corrupt compiler, by a cross site script attack ten years ago, fine, but not something that everybody should know is dangerous.