I would like to know if Firefox 1.6 or 2 beta 1 ar both protected by the avast! Web Shield by default because thanks to you I soon discovered Opera wasn’t fully protected by avast! in it’s default configuration -although Web Shield module is capable of protecting Opera’s surfing with a little tweak in avast4.ini
So, do I need to add the process name to the avast4.ini like already did with Opera browser (OptinProcess=OperaUSB.exe)? In this case, how I do it? Just put comas between processes names?
The regular release of firefox, current;y 1.5.0.6 (not 1.6) is covered and as far as I’m aware so is the firefox beta 2.0. As you mention it is no bi deal to resolve it if not, but I doubt you will have to do that.
As you say it may be not a big deal to resolve, but you see this issue with a power-user eyes and not with the common-Joe eyes; it would be great development team just add a field to do this within a nice GUI.
Since you don’t give me a 100% security about web scanning when surfing with FF I’ll need to see if the avast! icon starts to spin like crazy when loading a web page
avast simply scans the port 80 (http) accesses of programs in its “to scan” list. The name of the Firefox process is still plain old firefox.exe. avast does not know or care what version it is - just so long as it is firefox.exe and issuing port 80 http calls (and no way little old minor player Firefox can change that) then avast will scan it.
When it comes down to it … avast does not run on magic … it runs on logic.
If you will hide information from us … but this is not, after all, the default Firefox process.
I would place a small wager that this process is not included in the list of avast’s “to scan” processes (though I am not sure why avast continues to hide this information).
To ensure that it is scanned then you can add it to your OptinProcess line in the avast4.ini. Just make sure that you use a comma to separate it from any existing process already in that line (like OperaUSB.exe).
