For as far as I know, an Instance of SecurityManager can only be loaded once
inside a Java VM.
Within Netscape, there is a SecurityManager instanciation ever done at the
initialisation. So it should not be possible for a class, even loaded locally,
to instanciate its own.
The fact the security is at a lower level in local mode should be implemented
inside the SecurityManager implementation inside of Netscape's Java VM
implementation. The fact you work within your network on an Intranet application
should not change anything. The only question that Netscape asks itself
regarding an applet is : Is it comming from a file:/.... URL or an http:/...
one ? ( known by Applet's getDocumentBase() method ).
If you want to override this, you should try to unzip the JDK classes package
delivered with netscape, and replace their security management classes with
( use javap, the disassembler within the JDK to check classes prototype and
public Interface from *.class bytecode files. Option -l should help if you are
interesting in all prototypes, including private method/attribute and local
stuff as well)
So you should then just have the classes you need, putting back the .zip
archive in place from your modifications.
I hope this help,
***** THE CONTENT OF THIS MAIL IS MY OWN OPINION, FROM PERSONNAL INTEREST *****
***** IN NO WAY Sun Microsystem SHOULD BE LINKED WITH IT'S CONTENT *****