-=> Mocking Richard to Kurt <=-
(Mock, mOck, moCk, mocK)
KW> not that i want to be a stick in the mud or anything, but how did your
KW> company verify that their test bed really were all viruses?
RSJ> Let me guess, you are someone that works for a company that uses
RSJ> computers and are trying to make brownie points with your boss by
RSJ> suggesting how you guys can evaluate some anti-virus software, and now
RSJ> he has asked how to confirm contamination.
no, actually, i'm a complete independant here... i don't work for
anybody... i just know that the first mistake in a zoo test is usually a
poorly maintained zoo...
RSJ> This also gave us a quick builing function because we knew the series
RSJ> of files on the tape were clean, just put multiple copies out there
RSJ> first. backed it up completely as 1 server with 400,000 files. Then
RSJ> started contamination procedure and quit when we got 100,000 file
RSJ> comparison errors.
RSJ> Any file contaminated will not compare as being the same file.
this will detect file corruption, but how did you distinguish between
file corruption and infection? were the altered files executed after a
clean boot to see if the offspring of the first generation (ie. the
second generation) would also reproduce?
KW> ... think for us, pozo!...
RSJ> I don't get it.
did you ever read waiting for godot?
... think for us, pozo!...
--- Maximus 2.02
---------------
* Origin: Virus Watch BBS ,[(416)654-3814] (1:250/503)
|