News for hackers. Stuff that matters.
Re:What The Rails Security Issue Means For Your Startup by revelation on Thursday January 31, 2013 @07:27PM (#5148414)
What you are looking for is not "OO language", but "dynamic interpreted language".

In a traditionally compiled OO language like C++, classes cease to exist after compilation; there is no fully generic way to instantiate an object of a class by data determined at runtime. So this whole concept of deserializing to whatever the protocol specifies goes completely out of the door.

Re:What The Rails Security Issue Means For Your Startup by jrochkind1 on Thursday January 31, 2013 @10:50PM (#5149100)
So your conclusion is that dynamically interpreted languages are all insecure?

(You can instantiate objects with classes specified by data in Java too, although Java isn't usually considered exactly dynamicaly interpreted. In fact, there was a very analagous bug in Spring, as mentioned in many places in this comment thread. But anyway, okay, sufficiently dynamically interpreted to allow instantiation of objects with classes chosen at runtime... is the root of the problem, you're suggesting, if everyone just used C++ it would be fine?)

Re:What The Rails Security Issue Means For Your Startup by phil on Thursday January 31, 2013 @11:31PM (#5149219)
"Interpreted" is too restrictive. For example, Objective C provides NSClassFromString().
Re:What The Rails Security Issue Means For Your Startup by revelation on Friday February 01, 2013 @03:30PM (#5153278)
One could argue that since every call goes through a runtime messaging framework, Objective C is really just an interpreted language with pre-JITed function bodies.