Server based virus protection (AREV Specific)
At 01 FEB 2000 02:15:57PM Matt Sorrell wrote:
I have searched the list, and read a bunch of the different topics on virus protection and AREV files. The gist of what I learned is that you should have the virus protection programs exclude *.OV? files from it list of file types to be scanned.
Our network group is wanting to place McAfee virus protection software on the network that runs server-side, instead of relying on client machines.
I'm assuming the same rules still apply, that it's alright to do this as long as the OV files are excluded. Would it be better to just exclude the entire ARev directory structure, or is excluding the OV files all that is required?
Thanks,
Matt Sorrell
msorrel@greyhound.com
At 01 FEB 2000 04:25PM Victor Engel wrote:
You should exclude LK and OV files. If you exclude the whole directory, you leave them vulnerable to attack. If you can guarantee that only Arev generated files are there, then you may be OK, but I think with most setups (unless you are using the REVELATION user) this will not be the case.
I know on our setup, despite our warnings to the user community, Microsoft Office documents continue to be saved to the Arev directory. Microsoft Office documents are frequent targets of viruses.
At 01 FEB 2000 04:40PM Matt Sorrell wrote:
Victor,
Thanks for the info. I just got a little more info that might make a difference.
We are running on a Novell 4.x server, and the network guys want to install the McAfee NLM on the server for virus protection.
I'm still going to assume the stipulations are the same, that REV*.LK and REV*.OV files should be excluded.
Thanks,
Matt Sorrell
At 02 FEB 2000 01:35PM Victor Engel wrote:
Right. The thing is that both .LK and .OV are recognized extensions. The problem is that they are not recognized as Arev extensions but as something else (I don't remember what, but it doesn't really matter), so they are checked for the wrong format.