I have been getting a ton of hits through Google about people looking for further information on ActiveX KillBits.
Killbits are basically a way to stop IE (or anything based on IE) from calling an ActiveX bit to call another program. Like, for instance, say you want to stop Yahoo Jukebox (as detailed recently in the most recent MSFT patches) from starting up when someone clicks on a link or something in IE, with the link telling IE to launch the Jukebox.
Well, you can prevent this from taking place by setting a "killbit" in the registry, which will basically prevent a program from being launched from within IE. Detailed instructions are right here on MSFT's website. You can do this globally across an enterprise as well by using a GPO for Windows. I suggest a read of that website for your Killbit needs.
Subscribe in a reader
3 comments:
I'm not sure what your take on this is... my issue is that they continue to try to stuff the kill bit for ADODB.Stream down my throat, despite having manually cleared it many times! Problem is I've written code that uses ADODB.Stream integrally -- I just wish I could override this crap once and for all!
I'm not sure what your take on this is... my issue is that they continue to try to stuff the kill bit for ADODB.Stream down my throat, despite having manually cleared it many times! Problem is I've written code that uses ADODB.Stream integrally -- I just wish I could override this crap once and for all!
I'm not sure what your take on this is... my issue is that they continue to try to stuff the kill bit for ADODB.Stream down my throat, despite having manually cleared it many times! Problem is I've written code that uses ADODB.Stream integrally -- I just wish I could override this crap once and for all!
Post a Comment