3 ms·
In the 90s there was no compute-as-service and the difficulty in sanely running arbitrary yet potentially deliberately adversarial code was less well-understood
by pvg 6y ago
In the 90s there was no compute-as-service and the difficulty in sanely running arbitrary yet potentially deliberately adversarial code was less well-understood. The latter is maybe still not all that well-understood.
- jjtheblunt 6y agoWas "tomcat" and EJB the 90s version thereof?
- pvg 6y agoNot really, it would fall under the 'language runtime' category in the article. EJB was not really designed with the goal of isolating entirely arbitrary, intentionally adversarial code. That's a problem that's gone from 'near-future interesting' to 'current, important and practical' since the 90s - both on the client (browsers, phones) and the server.
- pjmlp 6y agoSure it was, that is what I have done several times with WebSphere.
- pvg 6y agoYou ran intentionally adversarial code with WebSphere?
- pjmlp 6y agoI run intentionally WebSphere security capabilities to contain EAR and WARs into their own little universe, alongside JEE security capabilites and managers. Everything that Docker sells was already possible with JEE application containers, just Java only.
- hinkley 6y agoTo be fair, there were a lot of CVEs because part of the sandbox in Java was capabilities-based, and the Achilles' heel of capabilities is that if you can see it, you can use it, and feature factory work has a bad habit of accidentally making things visible by exposing some parent object in an attempt to be helpful. I did like the permissions inheritance model quite a bit, but the hybrid ACL/capabilities system was always a bit schizophrenic.
- pjmlp 6y agoStill way less than C based technology, and besides most of them were related to Java Applets, a completely different stack than application containers like WebSphere.
- tptacek 6y agoNo, it wasn't; you couldn't keep code running in a WAR off the network. For a number of years, practically every sitewide pentest I did was gameovered by SSRF off Java application servers. I never even bothered to figure out how tight the isolation between co-resident applications was on those things.
- pjmlp 6y agoSure you can, by packing the network sensitive code into another Java library and using process internal bean calls across domains. Now if those guys didn't understood the WebSphere capabilities that is another matter.