Disabling IE Scripting in a Useful Manner?
hwyguy2 asks: "Do any Slashdot readers have any insight or pointers on how companies deal
with ActiveX in the IE browser? At the company I'm with, they have taken a
conservative approach, and have the browser configured to only allow ActiveX to internal corporate servers and disallow it anywhere else. Of course, locking that down also locks things like javascript, which the company choses to prompt. This creates many practical problems and user frustrations. It also
makes it a pain for programs that use ActiveX innocously (such as HoTMetal, which seems to like to use an Active X control to get an open file dialog box). Given the number of sites out there that now only work with IE (boo!), this tight configuration is getting harder and harder to support. Are there any good ways to address the ActiveX concerns (maybe filtering servers to block ActiveX or other mobile code concerns)?"
Security
Functionality
Guess which side of the fence ActiveX is on.
There isn't an easy answer that isn't going to be flippant.
The opposite of progress is congress
BTW, Proxomitron basically lets you apply regex-like filtering and search/replace to your incoming HTML, so it's useful for a *lot* of stuff.
Google Search for Proxomitron
Please consider making an automatic monthly recurring donation to the EFF
You can control the places where IE looks for ActiveX controls. The magic registry key is
t ernet Settings\CodeBaseSearchPath
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\In
By default you will see CODEBASE in the registry value. That means if there is a CODEBASE parameter in the OBJECT tag on the web page, IE will use it if the correct control version is not installed. However, you can also remove CODEBASE from the string and set this path to a location on your own network, where you place only the small set of trusted ActiveX controls you want your company to use. No other controls will be loaded.