8 ms·
If you read something like this [1], dated 1999, it seems like they had the right ideas. I guess it went wrong in the actual implementations. [1] http://www.s
by newsoul2019 7y ago
If you read something like this [1], dated 1999, it seems like they had the right ideas. I guess it went wrong in the actual implementations.
[1] http://www.securingjava.com/chapter-two/chapter-two-2.html http://www.securingjava.com/chapter-two/chapter-two-2.html
- hyperpape 7y agoBy total coincidence, I was reading about Java sandbox exploits just a few days ago: http://phrack.org/papers/escaping_the_java_sandbox.html http://phrack.org/papers/escaping_the_java_sandbox.html. It feels to me (not a security guy!) like there was something fundamentally too complex here. I wonder if part of the problem is that unlike the browser, there's no natural boundary. JavaScript is was originally built to live in a small self-contained world with specific access to the outside. Java was built with features for writing applications that could touch the filesystem, redefine classes, and everything else. It was also supposed to make everything safe, but that led to complex checks everywhere to try to distinguish privileged from unprivileged code.