Re: How and why?

Post #23,786 by acagle 1/10/02 2:41:23 PM Reply	Re: How and why? That's about it: how does Java (or Unix or Linux or whatever) actually go about making a "sandbox" that the executables can't muck things up outside of it? I have kind of a vague idea, but nothing really technical.
Post #23,796 by a6l6e6x 1/10/02 4:19:44 PM Reply	Re: How and why? [link\|http://java.sun.com/marketing/collateral/security.html\|Here] is Sun white paper thingie. The business end of the Java security model is conveniently described by using the metaphor of the Sandbox. The sandbox comprises a number of cooperating system components, ranging from security managers that execute as part of the application, to security measures designed into the Java Virtual Machine* (JVM) and the language itself. The sandbox ensures that an untrusted-and possibly malicious-application cannot gain access to system resources. Alex Men never do evil so completely and cheerfully as when they do it from religious conviction. -- Blaise Pascal (1623-1662)
Post #23,800 by Arkadiy 1/10/02 4:38:44 PM Reply	Re: How and why? In ActiveX, in order to draw a fish on your desktop, the object must have all permissions that you have. In Java, in order to draw same fish, the applet only has enough permissions to draw on desktop. ActiveX has all or nothing security model. Java could always do "some or all", and now it can do multilevel permission, depending on where the code comes from and who signed it.

Welcome to IWETHEY!