And this plug-in apparently makes IE runs circles around your broken pile of hacks in its original state. It’s no wonder your response is to claim it makes IE less secure — because in your world, it’s only secure if you control the code and the patching mechanisms. In everyone else’s, it’s secure if you set up permissions correctly to begin with, such as how in Chrome, plugins can only operate within the context of Chrome itself, never gaining access to the system resources unless a programmer can somehow not only crack their way out of the sandbox, but then go on to compromise the system proper.
Yes, I know, IE 7 and 8 have a “protected mode” that it can run in, which does this same kind of sandboxing — but that only works under Vista and Windows 7. Google Chrome will run under XP and IE6 as well. As I just pushed through the IE8 patch throughout my work network, and the bulk of the complaints are about IE’s speed decreases (though I’ve disabled frippery like accelerators and the welcome wizard in an attempt to mitigate that somewhat), I’m strongly tempted to distribute Chrome and this Chrome Frame plugin as well. It’d not only diminish the speed complaints, it’d significantly increase the security of my XP-based environment.