News for hackers. Stuff that matters.
Re:GET /browser.exe by ezyang on Friday October 12, 2012 @06:15PM (#4647099)
The Java sandbox was actually really close to something that worked well. If you look at the Java virtual machine, it's actually quite simple, and very easy to ensure that nothing "bad" happens. Where Java lost the battle was in the provisioning of APIs which, you know, actually let developers do things like draw windows or load trusted code dynamically: here, it suddenly became necessary to trust huge swaths of code to do the right thing, and the Java sandbox got fucked. If you look at all of the sandbox vulnerabilities, they are never "Oh, the JVM was implemented incorrectly" and always "Oh, some API wasn't implemented properly." That's the key observation.
Re:GET /browser.exe by dredmorbius on Friday October 12, 2012 @06:54PM (#4647213)
The other place Java lost the battle was in sticking to a closed, vendor-dictated implementation, that's slowly getting pulled into the massive hole of suck that is Oracle.
Re:GET /browser.exe by zzzeek on Friday October 12, 2012 @06:28PM (#4647139)
and browser.exe would make none of these mistakes because..... ?
Re:GET /browser.exe by ezyang on Friday October 12, 2012 @06:34PM (#4647149)
Because it's untrusted: it runs in the sandbox.
Re:GET /browser.exe by snatch_backside on Friday October 12, 2012 @11:59PM (#4647840)
That seems like a pretty elegant solution.
Re:GET /browser.exe by moe on Saturday October 13, 2012 @06:39AM (#4648294)
Sandboxes all the way down. Cf. Chrome.