The second lecture uses an interesting code snippet. An example written in java taken from a book written in 1986 used to explain a C vulnerability. Something seems out of place.
Haven't seen that lecture yet, but something sure does seem out of place : java first appeared in 1995. If there's a book from 1986 showing java code, those pesky time lords have been at it again.
Anyway, I can see some logic behind using an ancient example of a vulnerability : these things were problems back in '86, and yet now, 2016, we still haven't figured out how to prevent them. I could also see the logic behind using another language : many security flaws are language independent. "I'm using <insert language here>, so I don't need to worry about security!" - yes, you do.
5 comments
[ 3.9 ms ] story [ 14.1 ms ] threadAnyway, I can see some logic behind using an ancient example of a vulnerability : these things were problems back in '86, and yet now, 2016, we still haven't figured out how to prevent them. I could also see the logic behind using another language : many security flaws are language independent. "I'm using <insert language here>, so I don't need to worry about security!" - yes, you do.