Spyke

Replies

Comment on

Majority of Critical Open Source Projects Contain Memory Unsafe Code

Reply in thread

Not sure if that is even the point. The article is all about memory unsafe programming!!1!. But there is no context at all.

Sure, there are vulnerabilities because of unsafe memory handling. But I looked for some statistic which would bring unsafe memory handling into context with say the high profile vulnerabilities from the last few weeks / months. I haven't spent too much time on research but looking at some lists containing vulns from the last few months it seems as if all those pre-auth, priv escalation, directory traversal and whatnot very based on much simpler failures like wrong error handling or logical errors or missing code than unsafe memory handling.

I might be wrong, then please show me the numbers, but shooting at C/C++ because unsafe!!1! sounds like a very biased story there.

And while we are at it. I'd also be interested in C vs. (somewhat modern) C++.

Comment on

A Deep Dive on Creepy Cameras

I like this comment on that page, haven’t heard about it before: «Was done..in Stockholm a few years back. Someone copied the plates of the CEO of the company operating a toll road in the city and posted it online. Folks pasted it over their own plates and used the toll road all day. The ALPR dutifully generated an humongous bill…»