2 ms·
That's a really good point. I'm eager to hear a response. It certainly seems like you could just ban a bunch of byte codes and easily detect them. I must be mi
by mrfusion 12y ago
That's a really good point. I'm eager to hear a response.
It certainly seems like you could just ban a bunch of byte codes and easily detect them. I must be missing something.
- nl 12y agoGenerally speaking it's the data associated with the calls that is risky, not the bytecode itself. The way the JVM works is by having specific permission checks at points within the code, and they are enforced by the JVM. I think the CLR works in a similar fashion. You can run Python on top of the JVM and take advantage of this, but I think the version of Python (JYthon) is pretty old.