While I would recommend the update, it doesnt "fix all VBS virus problems", just makes it slightly harder for them to replicate. A better fix for all VBS virus problems is to completely disable VBS on your system.
This can be done by a) installing a real (tm) operating system . c) installing a really primitive/obscure operating system. c) completely undoing all facilities on your box for .VBS files to run You cant actually blow away windows scripting host in Win2K; it is viewed as a 'protected' part of the system and every time you delete the appropriate libraries it comes back. You can stop .VBS, .JS and .WSH files from being bound to WSH, which kind of reduces the chance of infection. You can leave Perl files bound to it if you have ActivePerl installed on the basis that there are no .pl viruses in the wild. Oh, and turn off activeX while you are at it -no point in securing the front door when the side window is wide open. Regarding what we were given in our mailbox http://www.symantec.com/avcenter/venc/data/[EMAIL PROTECTED] As usual the worm/virus writers get their code wrong. Havent they heard of unit tests and deployment tests yet? They need 'vunit' :-) ----- Original Message ----- From: "Alex Solofnenko" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, February 12, 2001 7:25 PM Subject: RE: Here you have, ;o) Please update your Outlook at http://officeupdate.microsoft.com (there is an auto update). SR1 fixes all VBS virus problems. Sincerely, Alexey N. Solofnenko.
