Spybot S&D Users

[Spybot]

Hi there,
Has anyone experienced an error after scanning with the latest updated
detections from 10/26/04? came up after latest update definitions only.

Scan results:
Open error while scanning for BackOrifice.B : Wininit.ini file was in use
while scanning...

Anyone?

 

[Bart Ady]

Hi there,
Has anyone experienced an error after scanning with the latest updated
detections from 10/26/04? came up after latest update definitions only.

Scan results:
Open error while scanning for BackOrifice.B : Wininit.ini file was in use
while scanning...

Anyone?

I got the same message. Should we be overly concerned?

Regards!

Bart

 

[jeffrey]

Hi,

Got the same error, but the wininit.ini file on my system is only a 75byte
file, not big enough for anything harmful. Did a scan with Pest Patrol and
it didn`t see anything amiss. Plus I have Spyguard, Spyblaster and Guard
Bar running and if something tried to get on my system, they would have to
go through them first. Just submit a bug report to them and see what they
say.

Jeff

 

[Will Denny]

Hi

There's no wininit.ini file here. How did you install XP?

 

[Sven Pran]

Hi there,
Has anyone experienced an error after scanning with the latest updated
detections from 10/26/04? came up after latest update definitions only.

Scan results:
Open error while scanning for BackOrifice.B : Wininit.ini file was in use
while scanning...

Anyone?

I got the same message, had to boot into safe mode command prompt to
get access to wininit.ini and found that it contained just two lines saying
something like:

[Rename]
NUL=C:\Windows\...\temp\...\gert0.dll

a dll module that simply doesn't exist on my system.

So I renamed the wininit.ini file to wininit.txt to see if wininit.ini would
be
missed.

That got me rid of this error only to present me with another same problem
referring to win.ini and Cabrotor

I am not going to lose much sleep over this!

regards Sven

 

[Bart Ady]

Hi

There's no wininit.ini file here. How did you install XP?

Followed the discussion here
(http://www.dslreports.com/forum/remark,11696649~mode=flat)
downloaded, installed the TX fix over the previous Spybot, ran it,
and came out clean.

Regards!

Bart Ady

 

[Steve Nielsen]

Followed the discussion here
(http://www.dslreports.com/forum/remark,11696649~mode=flat)
downloaded, installed the TX fix over the previous Spybot, ran it,
and came out clean.

Regards!

Bart Ady

What "TX fix"? Can you supply a link, please. All I can find is the
regular Spybot S&D 1.3 downloads.

Thanks
Steve

 

[Sven Pran]

What "TX fix"? Can you supply a link, please. All I can find is the
regular Spybot S&D 1.3 downloads.

I tried some links that has been announced here, and I either got a
message that the requested page didn't exist or a message to the
effect that I was not permitted to access that page.

Sven

 

[Bart Ady]

I tried some links that has been announced here, and I either got a
message that the requested page didn't exist or a message to the
effect that I was not permitted to access that page.

Sven

Have you tried majorgeeks.com
(http://www.majorgeeks.com/download.php?det=4392) ?

Regards!

Bart

 

[Sven Pran]

Have you tried majorgeeks.com
(http://www.majorgeeks.com/download.php?det=4392) ?

Yes, and when I selected "Author's site" (I do reside in Europe!)
I received the message: error 404: Datei nicht gefunden!"

But I finally managed to get it from one of the US mirror sites.

Thanks Sven

 

[Sven Pran]

Yes, and when I selected "Author's site" (I do reside in Europe!)
I received the message: error 404: Datei nicht gefunden!"

But I finally managed to get it from one of the US mirror sites.

Thanks Sven

I installed 1.3.1 TX and then ran check for updates

Three testruns of Spybot next resulted in the following

All three test runs resulted in the well known DSO Exploit, attempting to
fix this
resulted in Spybot "could not fix" and "did I want to run Spybot on next
startup"?

I did so with the same result.

Finally I logged on as my regular user (limited) and ran Spybot
"as administrator". Same result except this time Spybot froze completely
displaying the message that it was "creating a system checkpoint".

Looks as if I (with some regret) shall have to uninstall Spybot
completely from my system until they get this misery fixed?

Sven

 

[Spybot]

Problem solved with today's latest Spybot "advance library" update. Hope
everyone's experiencing this issue will clear as well.

 

[MowGreen [MVP]]

http://forums.net-integration.net/index.php?showtopic=23997

" A new update "Advanched check library" is released, which should
fix the bugs that appear since the detection update from 26.10.04
(win.ini/system.ini-problems). "

Translation : The 27.10.04 update replaces the advcheck.dll and the
False Positive is resolved.

MowGreen [MVP]
===============
*-343-* FDNY
Never Forgotten
===============

Hi there,
Has anyone experienced an error after scanning with the latest updated
detections from 10/26/04? came up after latest update definitions only.

Scan results:
Open error while scanning for BackOrifice.B : Wininit.ini file was in use
while scanning...

Anyone?

I got the same message, had to boot into safe mode command prompt to
get access to wininit.ini and found that it contained just two lines saying
something like:

[Rename]
NUL=C:\Windows\...\temp\...\gert0.dll

a dll module that simply doesn't exist on my system.

So I renamed the wininit.ini file to wininit.txt to see if wininit.ini would
be
missed.

That got me rid of this error only to present me with another same problem
referring to win.ini and Cabrotor

I am not going to lose much sleep over this!

regards Sven

 

[Sven Pran]

How To: Configure SpyBot Not to Flag DSO Exploit
http://forum.aumha.org/viewtopic.php?t=8435

MowGreen [MVP]
===============
*-343-* FDNY
Never Forgotten
===============

Quite useful. And what happens if some day another
DSO Exploit should occur that really should be taken care of?

Sven

 

[MowGreen [MVP]]

Spybot - Search and Destroy DSO Exploit Fix 1.3.1 TX
http://majorgeeks.com/download4392.html

" The DSO Exploit is a security gap in IE. Microsoft did already
repair this, so if you have all Windows updates and patches
installed, it will not be dangerous for your system. Spybot S&D will
still find it, because it contains an invalid value. Spybot S&D just
has to reset that value. Unfortunately, in the current version, it
sets again an incorrect value, so it is found in the next scan.
Please update your main program. "

Feel better now ?

MowGreen [MVP]
===============
*-343-* FDNY
Never Forgotten
===============

 

[Ed.]

Is this fix a beta or is it final. I saw one time about it being in beta.

Thanks

 

[Sven Pran]

Forget 1.3.1 TX

While it might still be available from some of the mirror sites it has
been withdrawn (from the home site). That was in fact the reason why
I got the messages that my attemt to retrieve the fix was rejected in
the first place.

The only thing you need to do is to run the latest update.

The DSO Exploit will still be there but you will avoid all the other
problems we rann into.

(If you have already obtained 1.3.1 then get rid of it! It was a bad beta).

regards Sven

 

[MowGreen [MVP]]

Ed,

This is really much ado about nothing . It's not an exploit per se,
rather a bug in the way Spybot detects the MS fix. Have a read here
for more details :
http://forums.net-integration.net/index.php?showtopic=17159&st=105#

If the page is moved or changes, the 8th page of the thread is here:
http://forums.net-integration.net/index.php?showtopic=17159&st=105#

It's the last post on the above page.

MowGreen [MVP]
===============
*-343-* FDNY
Never Forgotten
===============

 

[Rock]

Is this fix a beta or is it final. I saw one time about it being in beta.

It's an updated version.