«

How I get rid of DSO Exploit?, always there on Spybot scaners.
Thanks.

load the latest patch for spybot
"Galego" <> wrote in message
news:qpDDd.254$ k.net...
> How I get rid of DSO Exploit?, always there on Spybot scaners.
> Thanks.

Cubzilla wrote:
> load the latest patch for spybot
> "Galego" <> wrote in message
> news:qpDDd.254$ k.net...
>> How I get rid of DSO Exploit?, always there on Spybot scaners.
>> Thanks.

Or just follow the registry link (using start>run type regedit) that spybot
gives, and delete it! (In Win9x)

Brian G

"Galego" <> wrote in message
news:qpDDd.254$ k.net...
| How I get rid of DSO Exploit?, always there on Spybot scaners.
| Thanks.

Ignore it. MS patched that hole a long time back.

Here we go.
http://forum.aumha.org/viewtopic.php?t=8435





"Toolman Tim" <> wrote in message
news:84EDd.50392$...
>
> "Galego" <> wrote in message
> news:qpDDd.254$ k.net...
> | How I get rid of DSO Exploit?, always there on Spybot scaners.
> | Thanks.
>
> Ignore it. MS patched that hole a long time back.
>
>

This is used by MS, for its update monitoring. If you get rid of it, it
will come back again. It is required. Spybot sees it as a threat,
because of the nature in which it works. Do not worry about this one.
Jerry G.
======

Toolman Tim wrote:
> "Galego" <> wrote in message
> news:qpDDd.254$ k.net...
> | How I get rid of DSO Exploit?, always there on Spybot scaners.
> | Thanks.
>
> Ignore it. MS patched that hole a long time back.
>
>
Thank you, I use Mozilla Firefox, and I heard that it is safer than IE.
I will ignore it.

"Galego" <> wrote in message
news:rjGDd.351$ .net...
| Toolman Tim wrote:
| > "Galego" <> wrote in message
| > news:qpDDd.254$ k.net...
| > | How I get rid of DSO Exploit?, always there on Spybot scaners.
| > | Thanks.
| >
| > Ignore it. MS patched that hole a long time back.
| >
| >
| Thank you, I use Mozilla Firefox, and I heard that it is safer than IE.
| I will ignore it.

Here's the page I was looking for earlier:
http://forums.thatcomputerguy.us/lof...php/t8548.html
I don't recall exactly which MS patch actually took care of this though. So
even if you're not using IE, it may be a good idea to keep it updated.