News for hackers. Stuff that matters.
Re:Some Were Meant for C (2017) [pdf] by aap_ on Thursday April 25, 2019 @06:10AM (#19746575)
I was actually more looking for practical issues. Usually the code that I write doesn't even handle strings a lot. Maybe I'm just using other languages for when I do that or maybe I'm using other approaches where others would use strings or maybe I just subjectively don't find them so bad as others. I'd just like to see exactly what people are complaining about so I could find out why I usually don't.
Re:Some Were Meant for C (2017) [pdf] by coldtea on Thursday April 25, 2019 @10:05AM (#19748225)
>I was actually more looking for practical issues.

Those are not practical? Billions of dollars have been wasted on issues stemming from this...

Re:Some Were Meant for C (2017) [pdf] by aap_ on Thursday April 25, 2019 @10:23AM (#19748424)
I'd just like to see a concrete example for once.
Re:Some Were Meant for C (2017) [pdf] by coldtea on Thursday April 25, 2019 @11:02AM (#19748886)
Like, apart from tons of well known bugs, and vulnerabilities caused from string manipulation? How exactly did you miss news items, reports, posts, university lectures, books, and even your own personal experience, on them?

Or is the insinuation that we are hand-wavy about it, and you doubt the existence and scale of the problem? It's a well researched, well established problem, known for almost half a century.

https://en.wikipedia.org/wiki/C_standard_library#Buffer_over...

https://security.web.cern.ch/security/recommendations/en/cod...

http://www.informit.com/articles/article.aspx?p=430402&seqNu...

https://randomascii.wordpress.com/2013/04/03/stop-using-strn...

https://courses.cs.washington.edu/courses/cse341/04wi/lectur... (null termination)

https://www.geeksforgeeks.org/why-strcpy-and-strncpy-are-not...

https://www.owasp.org/index.php/Reviewing_Code_for_Buffer_Ov...:

And let's not even get into format string issues...