Adam Jack mumbled something vague about:
> > You can't tell which pages will have applets, but you _can_ mandate
> > that the users only use non-Java(tm)-aware browsers. (Yes, Netscape is
> > releasing such beasts.)
>
> My turn at playing the broken record. However - since Sun have left few
> centralized control options (using HTTP & user config) - I think this is
> a useful tip.
>
> Trap all http://*.class requests at the firewalls HTTP proxy. Denying
> them should affect only Java applets. (OK - application firewall
> soln only. But even packet filter only sites should have an internal
> cached HTTPD IMHO.)
Works great iff the person writing the page doesn't get wise and
rename the class file to MyApplet.wonky or some such.
I suspect that many people will try the *.class solution, and it will
quickly become standard for anyone who "really wants people to see
their cool applet" to rename it.
Mike
--
#> Mike Shaver (shaver @
ingenia .
com) Ingenia Communications Corporation <#
#> Technical Specialist -- will tame sendmail(8) for food <#
#> <#
#> "You are a very perverse individual, and I think I'd like to get to <#
#> know you better." --- eric @
reference .
com <#
Follow-Ups:
-
Re: Java
From: Adam Jack <ajack @
corp .
micrognosis .
com>
References:
-
Re: Java
From: Adam Jack <ajack @
corp .
micrognosis .
com>
|
|