Script Shield not working

[LorenzoC]

I have reported this for v.6 already, same problem with v.7.

Windows XP Home SP3, all updates installed.
Avast v. 7.0.1407

Script Shield shows zero scripts scanned using Firefox and Opera.
It seems to work using Internet Explorer.

[AdrianH]

ScriptSheld does not work with Opera. There is no active x ustilised in Opera which is why it is less prone to malware scripts, Spywareblaster has no plugin for Opera for the same reasons, there is nothing to block.

Which version of Firefox is it not working with?

[LorenzoC]

Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2

BTW, I guess ActiveX is a completely different topic.

[Gopher John]

SpywareBlaster has no active components;  there is no plugin for any browser.  SpywareBlaster's protection is totally passive.  Once the user has used SpywareBlaster to inoculate his machine and closed the interface, no part of it is running in memory.  The only protection that is added to Firefox exclusively is blocking cookies from certain domains.  Links to how it works https://www.javacoolsoftware.com/support/index.php?_m=knowledgebase&_a=view&parentcategoryid=4&pcid=0&nav=0.

I've had my machine on for 3 hours using Firefox.  ScriptShield shows 211 scans, likely from visiting this forum, and a few other sites where I allow JavaScript.

[LorenzoC]

@Gopher John:
I am happy if Script Shield works for you. It was a nice day here today and I took a walk in the park.

That said, Script Shield still shows zero hits with Firefox here while it scores with Internet Explorer.
I guess there must be a reason, like the OS version and/or some MS component/runtime needed.

[Gopher John]

@Gopher John:
I am happy if Script Shield works for you. It was a nice day here today and I took a walk in the park.

That said, Script Shield still shows zero hits with Firefox here while it scores with Internet Explorer.
I guess there must be a reason, like the OS version and/or some MS component/runtime needed.

Well, we have a rainy day here.

I have WinXP Pro SP3 fully patched, close enough that the OS shouldn't matter and Firefox is the same.  It doesn't have to be MS that is causing your problem, but another 3rd party program (even one that was uninstalled but left behind components of it).  Former security programs are a likely candidate.

An extension in Firefox may be the culprit.  You could start Firefox in Firefox Safe Mode, and see if Avast Script Shield triggers when you visit what you consider a known safe site with JavaScripting.  This forum is a good candidate, as it does trigger Script Shield for me.

[nigel mansel]

I had the same with a laptop running windows 7,UN-installing chrome that was downloaded without my consent has fixed the problem.

script shield is fully working now in Firefox.

[LorenzoC]

Nope, there isn't and there wasn't any "security" thing on this system and I had the same problem with Avast v.6.
It was reported December 03, 2011 and confirmed, read here:
http://forum.avast.com/index.php?topic=89783.msg715353#msg715353

I have only ADBlockPlus and dictionary as installed extensions, I will try to disable ABP later.

[Gopher John]

@LorenzoC

I doubt that it's AdBlock Plus, as I'm using it with EasyList, Easy Privacy, and Malware Domains filter subscriptions.

If you've added some modifications to UserChrome.css, those might cause an issue.  With Firefox Safe Mode, I believe UserChrome.css isn't used.

[LorenzoC]

Never touched UserChrome.css in my life.
I have tested Avast with a brand new Firefox profile. No extensions installed. Only Flash plugin present.
Same, zero hits from Script Shield.

The whole system is relatively new, it is an old laptop I use seldom and it was completely reinstalled not long ago.
Like I said above, there wasn't any other "security software".
I have installed only Avast v.6, which had the same problem.
I have unistalled v.6 and installed v.7, still the same problem.

At this point my guess is either a bug in Avast or Script Shield needing some system configuration, like some Visual C library installed or .Net runtime.
It would be nice to hear something from devs.

[Gopher John]

At this point my guess is either a bug in Avast or Script Shield needing some system configuration, like some Visual C library installed or .Net runtime.
It would be nice to hear something from devs.

I agree about the devs.  It seems that your setup is perfect for their testing.  It has the problem and is basically unadulterated.  Perhaps they'll see this.

The only .NET here is Microsoft .NET Framework 1.1, which was before MS started putting the add-ins into Firefox.  I do have three entries in my Add/Remove Programs for Visual C++:
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161
Microsoft Visual C++ 2008 Redistributable - KB2467174 - x86 9.0.30729.5570

FYI, there is a Avast! 7 R2 beta available, which you might have seen.  http://forum.avast.com/index.php?topic=94790.0  Asyn has the Script Shield issue with the R2 beta and Firefox 3.6.27 http://forum.avast.com/index.php?topic=94790.msg755653#msg755653.  I haven't installed this new beta yet.

[LorenzoC]

I have to compare my system configuration with yours, besides I already know there isn't any .Net installed on mine.

Yes I have seen the RC but I don't think it makes any difference.
The issue with XP Home SP3 - Firefox - Scritp Shield it there since some Avast v.6 release.
I cannot say which release exactly but I guess it is nothing new.

The only feedback I got so far was from DavidR, confirming the issue on his own machine and stating:
"I have tried to get someone to look into this."

[LorenzoC]

I have got only:
Visual C++ 2008 Redistributable - x86 9.0.30729.4148

No other "redistributable" either any .Net installed.

[Gopher John]

Avast 7 has a "Generate Support Package" on the Maintenance tab.  Perhaps if Avast gets involved in the Script Shield problem, there would be enough information to find out why it works for some and not others in Firefox.

[LorenzoC]

Yes.
But if you ask me I think the devs already know of the issue but either fixing it is very low priority (more serious issues, XP being backwards compatibility) or it requires too much work that they think it is not worth it.

Anyway it would be nice to get a feedback.