4 ms·
I was there. We had plenty of those kind of problems in those days. I also had the classical training of which you speak, but the industry was far ahead of ac
by fcbrooklyn 8y ago
I was there. We had plenty of those kind of problems in those days. I also had the classical training of which you speak, but the industry was far ahead of academia in terms of actually dealing with that kind of thing. The reason pre-internet is relevant is that the penalty for a buffer overflow in 1995 might be a crashed app, or maybe a corrupted file. It was only later that the penalty became "getting pwned by some sophisticated bit of malware and needing to send monero to someone to get your compter back".
- matt_the_bass 8y agoThanks. That’s a good example.
- danmg 8y agoBuffer overflows to gain remote access to a computer were fairly well known in 1995. "Smashing The Stack for Fun and Profit" (http://phrack.org/issues/49/14.html http://phrack.org/issues/49/14.html) came out the following year. Most people weren't really writing network facing code though, so most buffer overflows were as you described. They just resulted in seemingly random crashes.