DSO Exploit picked up by Spybot (registry change by Microsoft). . .should I delete it or leave?

Joe,

What I don't understand is that it appears that the source is Microsoft.  Is that correct?  Is this change in the Registry something that Microsoft has placed on my PC to fix the IE security hole, or is it a breach of IE security?  (BTW, when XP asks me to download Windows updates, I do it.) 

Thanks!

Ed:

As far as I can tell,  Spybot is saying that there is
a security hole in IE6 that it can fix. I don't think it
is saying  that the hole has  been breached. Whether
 it was in the original IE, or in a subsequent patch, I
don't know. All I can say is I let Spybot fix the problem
months ago,  without any problems since.

I always download all critical security patches from
the MS update site too, although I usually wait a few
days. Sometimes the patches need patches. I've even
seen one critical update offer rescinded the next day,
before I downloaded it. Presumably it had an error, or
perhaps wasn't for my system (W98SE).

I trust Spybot  a lot more than MS, after a year of use.
My 2 cents, anyway.

Here is a link to a fix for the DSO exploit. I haven't tried it myself http://www.nsclean.com/dsostop.html

Article found on topic, looks to be dated alittle over a year ago:

The "DSO Exploit" was first reported by GreyMagic Software of Israel on February 27, 2002 and a "workaround" for Microsoft's defective code was provided by Axel Pettinger and Garland Hopkins on March 3, 2002 involving the editing of the Windows registry to alter values contained within Internet Explorer's Internet Zones configurations. Because many computer users are extremely nervous (and justifiably so) about manually editing the Windows registry, owing to years of warnings and advisories as to the dangers of editing the registry, Privacy Software has provided this FREE utility to safely do it for those who do not feel confident running and editing "Regedit." We have, as we have many times before, provided this software for NO CHARGE to our customers as well as the general public to solve a serious problem as of the time of this release, and Microsoft is in their usual denial mode, not having provided a patch for a substantial amount of time. Since Microsoft won't fix it, we have to.

I'm not clear on what the hazzard of this exploit is, but I believe Microsoft has since patched this, though I could be wrong.  But I'd try rerunning Windows Update to be safe.