News for hackers. Stuff that matters.
Re:Let’s sunset C/C++ by gizmo on Friday August 14, 2015 @08:33AM (#10059766)
There is a huge difference between a program that computes the wrong answer and one that corrupts memory, hijacks a shell, and installs a rootkit.

Javascript is turing complete but it's trivial to write a (slow) javascript interpreter in Python that allows anybody to run any javascript program without any risk to their machine. No memory attacks possible. To privilege escalation possible. No unchecked stack overflows. The system would be sandboxed and secure. It will just work or fail gracefully.

It's only when we increase the complexity of our runtimes a thousand fold and when we cut corners to squeeze out higher performance that all the nasty vulnerabilities start to creep in.

Re:Let’s sunset C/C++ by sklogic on Friday August 14, 2015 @09:30AM (#10059996)
It must be really slow in order to avoid attacks like this one: https://github.com/IAIK/rowhammerjs
Re:Let’s sunset C/C++ by JoeAltmaier on Friday August 14, 2015 @09:06AM (#10059897)
For pure Java perhaps. But native code is inevitable, and it has no such protection. So in practice Java is not a lot of protection.
Re:Let’s sunset C/C++ by piva00 on Friday August 14, 2015 @10:23AM (#10060233)
I didn't understand how Java relates to his comment about JavaScript + Python.
Re:Let’s sunset C/C++ by JoeAltmaier on Friday August 14, 2015 @11:47AM (#10060768)
Sorry, its because I'm an idiot. Anyway, secure languages use native code, and that's still a problem.