News for hackers. Stuff that matters.
Re:CWE Top Most Dangerous Software Weaknesses by pjmlp on Thursday July 13, 2023 @09:10AM (#36708564)
You mean tecnhology like bounds checking, invented during the 1950's decade, with the creation of Fortran, Lisp and Algol, and every other language derived from them, with exception of C, C++ and Objective-C?
Re:CWE Top Most Dangerous Software Weaknesses by geodel on Thursday July 13, 2023 @11:35AM (#36710877)
And why the whole world wrote so much code in C, C++ and Objective-C when bound checking existing long before these languages without boundcheck?
Re:CWE Top Most Dangerous Software Weaknesses by pjmlp on Thursday July 13, 2023 @11:56AM (#36711312)
It started like this,

"Although we entertained occasional thoughts about implementing one of the major languages of the time like Fortran, PL/I, or Algol 68, such a project seemed hopelessly large for our resources: much simpler and smaller tools were called for. All these languages influenced our work, but it was more fun to do things on our own."

-- https://www.bell-labs.com/usr/dmr/www/chist.html

Then source tapes with an almost symbolic license price for its time, and a commentary book did the rest.

Re:CWE Top Most Dangerous Software Weaknesses by j16sdiz on Thursday July 13, 2023 @12:55PM (#36712338)
with bounds checking, out of range index still trigger exception or runtime error. Many of them results in DoS.
Re:CWE Top Most Dangerous Software Weaknesses by pjmlp on Thursday July 13, 2023 @01:42PM (#36713101)
Much better than silent data corruption.

Then there is the whole issue of making it more interesting to look elsewhere instead.

When a door is locked I can still break in by throwing a rock to the window, yet most people do lock the door nonetheless, while most thieves only bother to break the window if there is anything actually valuable in doing so.