Automatic scanning of downloaded files

Hi,

I use GetRight as a download manager. Is it necessary to configure GetRight to use NOD32 to scan downloaded files "when done", or will AMON do this automatically without further setup?

If I need to set GetRight up, what command line executable do I specify? Is it nod32.exe ?

I have searched this forum, but got conflicting messages.

Thanks in advance.
Chris

 

Well, I just tried it out and it worked fine. I configured GetRight to use "nod32.exe" to scan files once they are downloaded. It worked like a charm. Just configure GetRight to use whatever your path to nod32.exe is (e.g. "x:\program files\eset\nod32.exe")

Rick

Rick

 

I would like to have NOD quit if the file is clean. I have the command line /scanfile+ /scanboot- /scanmbr-.

 

/quit+ should exit you out if nothing is found.

 

I don't use GetRight, but I was interested in the orginal question nonetheless. Is it necessary to add an additional command line scan? Here is my thinking... AMON can be configured to scan files on "Open", "Create", or "Execute", so wouldn't any download involve the application in question causing a file "Create" event which would trigger AMON? This intrigued me because it also got me to thinking... most browsers temporarily cache on the harddrive a significant amount of the downloaded HTTP content, so is IMON HTTP functionality in the beta sort of duplicating a scan that AMON will also repeat in many cases? Just curious.

 

I'm happy to be wrong here . . . but it seems that you have to be very careful about how you configure NOD32 for any type of scan.

For example - NOD32 will not scan rar files in it's default settings. Even when you turn on 'scan archives' or add /arch+ to a command line.

I had to set NOD32 to scan 'All Files' to get it to scan rar file. Rar archives are probably the most popular compressed file type on the net. Other issues seems to be that when you turn on scan archives - NOD32 scans the file then reports that no files inside the archive were actually scanned . . . that's dangerous because it looks like it's done the scan but it really hasn't. It's even worse if you added /quit to the command line becuase you don't see the scan results and realise what's (not) happened.

This seems like a real oversight in NOD32 . . .

I'm gonna play with it's setting some more and see if I can add rar files to the standard list of files to scan.