> I'll mention that Security-7 (www.security7.com) has a product that
> will look through the Java classes or ActiveX controls and allow you
> to block things that you don't like. (Thus, you could block all Java
> that calls the file io classes.)
It's not possible for it to do that even in theory for general ActiveX
controls, because they can contain arbitrary '386 instructions, possibly
encrypted or compressed with unknown algorithms to reduce size or protect
intellectual property.
For Java, I suppose you could do it. The problem is that the authors of
legitimate applets will have no way of knowing what the rules they're
subject to are. It's better to make that sort of thing explicit in the
specification for the applet language even if that prevents you from
doing some useful things.
References:
|
|
