Scanning last downloaded file

[dealdieboy]

Thank everyone for your contributions. Conclusion is: no manual scanning, or remark in the downloadmanager  because the webshields do this control!

[Simion]

Thank everyone for your contributions. Conclusion is: no manual scanning, or remark in the downloadmanager  because the webshields do this control!

Actually, you should add ashquick.exe to LeechGet. Web Shield only scans traffic on port 80 which is not a port that LeechGet uses. But unlike Avast 4, you will not see a pop up every time Avast scans a download. Instead you will only see a pop up when Avast finds malware in a downloaded file.

[DavidR]

If the web shield doesn't scan it because it isn't using port 80 you also have the fall back of the file system shield scanning newly created/modified files (depending on file type, primarily those that present an immediate risk, e.g. executables, .exe, etc.).

[dealdieboy]

Ok: I've added this in Leechget: C:\Program Files\Alwil Software\Avast5\ashQuick.exe

[doktornotor]

Actually, you should add ashquick.exe to LeechGet. Web Shield only scans traffic on port 80 which is not a port that LeechGet uses.

Errr... so, what port it uses? It downloads something from a webserver via a port on which the webserver is not running at all? Miracle? I guess you are kinda confused here.

[Simion]

Ok: I've added this in Leechget: C:\Program Files\Alwil Software\Avast5\ashQuick.exe

[Simion]

Actually, you should add ashquick.exe to LeechGet. Web Shield only scans traffic on port 80 which is not a port that LeechGet uses.

Errr... so, what port it uses? It downloads something from a webserver via a port on which the webserver is not running at all? Miracle? I guess you are kinda confused here.

No confusion here. DMs use various ports, often in the 3-4 thousand range. But NONE of them use port 80. I suspect you are confusing user ports vs. server ports.

[doktornotor]

No confusion here. DMs use various ports, often in the 3-4 thousand range. But NONE of them use port 80. I suspect you are confusing user ports vs. server ports.

Eh... No, I don't confuse anything. Go download something like CurrPorts and look at what your browser does. I guess you won't claim that the HTTP traffic there isn't checked either.

[Simion]

No confusion here. DMs use various ports, often in the 3-4 thousand range. But NONE of them use port 80. I suspect you are confusing user ports vs. server ports.

Eh... No, I don't confuse anything. Go download something like CurrPorts and look at what your browser does. I guess you won't claim that the HTTP traffic there isn't checked either.

We're not talking about browsers here, we are talking about download managers, like Leechget, etcetera.

[Hermite15]

see screen shot >>>>   (downloading Ubuntu)

This said the download's an iso and it won't be scanned by the web shield (fortunately). Also, although that's port 80 the web shield wouldn't scan a download done through an external downloader >>> so ashquick could be needed, if the FileShield wasn't there (ISO excluded as well btw, and no need to go nuts scanning it through ashquick)

[doktornotor]

We're not talking about browsers here, we are talking about download managers, like Leechget, etcetera.

I know what we are talking about. Your so called download manager is not anything else but a specialized kind of browser intended for convenient downloading (as long as you are downloading from web and not via FTP, BT or something else). See screenshot attached. So yes, it is scanned by the webshield and no, manual scanning is not needed since you don't need to scan the same thing 3 times.

[Hermite15]

what you see is not the actual download being scanned by the web shield, it's the caching of it in Firefox. Keep your download link in your download manager. Download again later directly from the DM when the browser is closed, it won't be scanned.
 The webshield might scan on port 80, it only works with browsers (what's commonly called browsers) and not with download managers. Doesn't matter whether DMs are browsers or not, only a few "browsers" are compatible with Avast webshield.

[doktornotor]

what you see is not the actual download being scanned by the web shield, it's the caching of it in Firefox. Keep your download link in your download manager. Download again later directly from the DM when the browser is closed, it won't be scanned.

Well, that'd be a no. I don't use FF and as a matter of fact, I didn't use any "browser" to leech it, I simply added the download link to FDM manually. As clearly shown on the screenshot, yes, it is scanned by the webshield.

[Hermite15]

well nothing downloaded directly from FDM has ever been scanned by the webshield on my system you must have a special version

edit: I tried once earlier today, and another time just now, not scanned

(your screenshot doesn't prove anything)

[Simion]

well nothing downloaded directly from FDM has ever been scanned by the webshield on my system you must have a special version

edit: I tried once earlier today, and another time just now, not scanned

(your screenshot doesn't prove anything)

Nor on my system. I'm running a download now - two outbound TCP connections on ports 4471 and 4472. Nothing being scanned by Avast. I added ports 4471 and 4472 to the Redirect Settings. Nope, no scan.