Bypassing Netscape Sandbox Security for Java Applets
Saurabh Jang
Hi,
I had a query about how to bypass the "sandbox security" restrictions imposed
by Netscape 4.04 (if it matters I am on a Solaris 2.5.1 platform) for
an applet which I have written and would like others in my workgroup to use.
The web browsers that we use are all configured to use an http proxy and
although no proxy is specified for all hosts in mot.com, this doesn't help.
The applet will be downloaded from host A and will talk to a CORBA server
object on host B. Host A is within the mot.com domain, but host B does not
belong to any (NIS) domain within our network. It does have an entry in the
NIS hosts table, so people can use symbolic host names to refer to this
host however.
How can I allow Netscape to let the applet downloaded from host A
talk to host B?
Can I somehow "certify" this applet for users in my workgroup and thereby
bypass the normal restrictions?o
What if I tell my users to use the "file://" protocol to download the applet
instead of "http://"?
Saurabh
P.S.
If replying via email please use ja...@eis.comm.mot.com, and not the
Reply-To in the header of the post.
Thanks.
--
Saurabh Jang, Senior Software Engineer, Motorola Inc. ja...@eis.comm.mot.com
Greg Berigan
> I had a query about how to bypass the "sandbox security" restrictions imposed
> by Netscape 4.04 (if it matters I am on a Solaris 2.5.1 platform) for
> an applet which I have written and would like others in my workgroup to use.
You can't. If you could, it would be a serious security violation.
> The applet will be downloaded from host A and will talk to a CORBA server
> object on host B. Host A is within the mot.com domain, but host B does not
> belong to any (NIS) domain within our network. It does have an entry in the
> NIS hosts table, so people can use symbolic host names to refer to this
> host however.
>
> How can I allow Netscape to let the applet downloaded from host A
> talk to host B?
Have the applet talk to host A and have host A talk to host B. Or don't
use applets and instead use Java applications which don't have this
restriction.
Any and all communication that Java applet needs to make to machines other
than the one that served it must be done through the machine that served
it.
For further information, choose a group under comp.lang.java.*.
--
_-<#)-=# http://cse.unl.edu/~gberigan/War-of-the-Worlds/
___/___
_-~_--<###) Due to widespread abuse, I no longer read any messages
<~c>' __--< from users who employ munged addresses in their headers.
\_--=____#) Richard Hart and Justin Gunn of C|NET, this means you too.