RE: Calling other code in Java applications and applets

> I don't have any hints, but I think people need to be aware up front
> that calling native code from a Java applet disables
> any security that might otherwise be enforced for the applet.  

This, of course, presumes that the native code in question is less 
robust/trust-worthy than that Java runtime and the browser. It's
not obvious to me why this should be the case.

regards,
-Blake (who figures its all a reputation thing again)

No that wasn't  my point (that the native code is less
trustworthy than the Java runtime.)    My point was just
that any security measures that restrict applets do not restrict
anything that an applet causes to happen via a native method. 

For example one security restriction is that applets aren't allowed
to read files.   If an applet calls a native method then that native
method can read any files it wants.    I'm talking about the model,
not about the quality of implementation.     I'm not saying it's 
a bad or untrustworthy thing to do (call native methods), I just
thought it was worthwhile to point out that once you call a DLL 
from an applet, you have effectively chosen to disable the application
level SecurityManager.  It's your call as to whether this is a problem
or not.   

Marianne