Firefox 17.0 and Script Shield

[EmoHobo]

By the way the manual def update does not "steal" any dll's, it's only manual program update!

So back to my original question, when is Avast fixing this?

When they release a new version, and I sure their well be another beta stage coming soon since users are having problem with Avast on W8 if I'm not mistaken

Is it really a huge deal that the script shield doesn't work?  I mean I use NoScript and I have all the other shields, so am I in immediate danger that is worth the risk of me going and messing with things?

[EmoHobo]

So back to my original question, when is Avast fixing this?

Well, the fix is in the patch.

Ah, so it's just not mass released yet.

[Asyn]

Is it really a huge deal that the script shield doesn't work?

As you use NoScript anyway, no.

[EmoHobo]

Is it really a huge deal that the script shield doesn't work?

As you use NoScript anyway, no.

Then I will just wait for the mass release of the update, thanks for putting up with my stubbornness.

[Asyn]

Then I will just wait for the mass release of the update, thanks for putting up with my stubbornness.

No problem.

[EmoHobo]

I am torn, I'm so paranoid about doing it, but I'm also super paranoid about damaging something.

[been]

I applied the patch then lost it in a manual update. Could anyone advise what the risk is (as a percentage?) of using Firefox without script shield functioning (in comparison with using Firefox with script shield working)? 

[DavidR]

No one can give you that answer as we don't know your browsing habits. In all honesty though it isn't so long ago that there was no script shield in the avast free version (only in Pro/paid versions) and we did just fine didn't we.

If you are using firefox then NoScript is an add-on that I believe you should be using anyway, with or without the script shield.

[pk]

Please follow these steps to apply patch:

1. Close all your running web browsers and turn off self-protection mode (settings -> troubleshooting).
2. Download patched version to \Program Files\AVAST Software\avast:

• http://public.avast.com/~kurtin/patches/ap2012-11-23-001/aswJsFlt.dll (32-bit & 64-bit OS)
• http://public.avast.com/~kurtin/patches/ap2012-11-23-001/aswJsFlt64.dll (64-bit OS only)

3. ** NEW ** Download .sum file (save it to the same folder as .dll):

• http://public.avast.com/~kurtin/patches/ap2012-11-23-001/aswJsFlt.dll.sum (32-bit & 64-bit OS)
• http://public.avast.com/~kurtin/patches/ap2012-11-23-001/aswJsFlt64.dll.sum (64-bit OS only)

       Now avast won't replace your patched version with original DLL file.

4. Turn on self-protection.

[Samson63]

Thanks pk 

[EmoHobo]

Just followed those instructions, how do I know if it's working?

Actually I can see the script shield scanning again, so it works fine.

Thanks PK and now I don't need to worry about manual updates ruining this?

Edit: In the future will this cause any issues for users who applied the manual patches like this?

[pk]

Thanks PK and now I don't need to worry about manual updates ruining this?

That's correct (otherwise, it means my .sum files were generated incorrectly).

Edit: In the future will this cause any issues for users who applied the manual patches like this?

No, next program update will be avast8 and this .DLL will be automatically replaced with new version.

[EmoHobo]

Thanks PK and now I don't need to worry about manual updates ruining this?

That's correct (otherwise, it means my .sum files were generated incorrectly).

Edit: In the future will this cause any issues for users who applied the manual patches like this?

No, next program update will be avast8 and this .DLL will be automatically replaced with new version.

Great to know and I just attempted a manual update and the .dll were not replaced as they are still scanning scripts, thanks for working on these for us and getting them out to us before the next big update.

[jrace]

Please follow these steps to apply patch:
............snip...........

Works perfect - so, hitting the "Program Update" button does not exchange the new dll's anymore. 
Thanks, pk!


Edit: The .sum files assure the survival of the new dll's even under conditions of a "Program Repair".

[been]

Thanks PK!