V
Virus Guy
Guest
RJK wrote:
<span style="color:blue">
> I'd rather argue with him about, (paraphrased a little
,
> "the age of the A/V programs isn't relevant but, I don't think
> it would do any good."
> e.g. AVG seem change their .DLL contents and filenames almost
> as often as they supply signature pattern updates, </span>
Ok, if AVG is a moving target, good for it. I'm not saying that's not
(I've never owned or used AVG).
Based on the writeups for Storm, there seem to be lots of anti-malware
products that don't change their process names.
(tangent - some writeups say that Storm also turns off some P2P apps -
anyone know why it would do that?)
<span style="color:blue">
> ...I feel that my argument is already partly won because his,
> (IMHumbleO), flawed methodology, and views, has already got his
> systems a virus or two !</span>
<span style="color:blue">
>
</span>
When you manage systems being used by a few monkeys, you can't always
be watching over their shoulder...
<span style="color:blue">
> I'd rather argue with him about, (paraphrased a little
> "the age of the A/V programs isn't relevant but, I don't think
> it would do any good."
> e.g. AVG seem change their .DLL contents and filenames almost
> as often as they supply signature pattern updates, </span>
Ok, if AVG is a moving target, good for it. I'm not saying that's not
(I've never owned or used AVG).
Based on the writeups for Storm, there seem to be lots of anti-malware
products that don't change their process names.
(tangent - some writeups say that Storm also turns off some P2P apps -
anyone know why it would do that?)
<span style="color:blue">
> ...I feel that my argument is already partly won because his,
> (IMHumbleO), flawed methodology, and views, has already got his
> systems a virus or two !</span>
<span style="color:blue">
>
When you manage systems being used by a few monkeys, you can't always
be watching over their shoulder...