News for hackers. Stuff that matters.
Re:That Pretty Much Wraps it Up for C by CSDude on Friday April 11, 2014 @08:14PM (#7576321)
Please, it can happen in any language, it depends on how you write it. If you do not sanitize your inputs you get sql-injected, and is this fault of SQL or you? I agree it is harder to write C code safely, but this was a stupid bug, not actually a C incompetence. You could allocate a large buffer in Java, and you could use `System.arraycopy(array, 0, part, 0, size);` instead of OpenSSL: `memcpy(bp, pl, payload);` both lacks only a boundary check and language provided checks will not help you in Java. Java is given as an example language that provides boundary checks. It applies to others as well.
Re:That Pretty Much Wraps it Up for C by prospero on Friday April 11, 2014 @08:22PM (#7576340)
Sure, but that's bounded by the size of the buffer in Java. A bad boundary to the arraycopy in Java will throw an exception, not give you the contents of memory beside the buffer. These are not comparable failures.
Re:That Pretty Much Wraps it Up for C by jibsen on Saturday April 12, 2014 @04:30AM (#7577320)
As I understood it, part of the problem was that they rolled their own memory handling which cached allocations [1].

Otherwise, I imagine system memory protection would have found this much sooner.

[1]: http://article.gmane.org/gmane.os.openbsd.misc/211963