First off, I will say that I am happy to see that there is a fix for this ActiveX bug as it could otherwise create hardship for a lot of trusting Internet Explorer users. Clearly, I am not affected as both my platform and browser do not fall into this category. But a lot of you out there might want to look into making the registry adjustments suggested in the linked piece above.

Something tells me, however, that this is hardly the only serious exploit to hit Internet Explorer since going from 6 to 7 and now 8. But to be fair, I can think of a number of exploits being just as malicious for Firefox as well.

For my money, I always make a practice to simply disable the stuff that is in a position to do me the most harm. While not always as straightforward as we might like, I choose to disable Java in all browsers and I avoid any use of ActiveX like the plague.

Now this is just my own approach. Perhaps you have one that is a little less extreme? If so, I would love to hear about it. Just hit the comments here and share your own thoughts on how to best avoid nightmare scenarios like this with your browser.

[rsslist:http://rss.api.ebay.com/ws/rssapi?FeedName=SearchResults&siteId=0&language=en-US&output=RSS20&floc=1&afmp=&sacqy=&sacat=-1&fcl=3&sacqyop=ge&satitle=ActiveX&sacur=0&frpp=25&afepn=5336207425&sabfmts=0&dfsp=32&saprclo=&ftrt=1&ftrv=1&saprchi=&customid=&sorefinesearch=1&saobfmts=exsif&fss=0&catref=C5&saslc=0&saaff=afepn&from=R14&nojspr=y&saslop=1]