Daynotes on a budget

This originally started as an on-line technology support journal - a list of what I did to whom. I sanitized it, but the notes are still here.  Sort of a moving violation, if you will, of privacy.  Suggestions, recommendations, recriminations, etc., welcome - send them here.  Thanks!

Friday, May 5, 2000

I'm reminded of a book that was out a couple of years ago; 5/5/2000 - apparently (I've never read the thing) it predicted disaster of biblical proportions.  Pretty close.  Not dead-on, but close.

This week was swallowed whole by mosquitos.  Not really, but it sure feels like it.

We received in two new PCs.  Unfortunately, my predecessor left few if any instructions on their configuration, despite pleas to the contrary.  So, we're learning as we go. If we're lucky.

The tail end of the week was disastrously consumed by three words everyone loves to hear - "ILOVEYOU". 

I received a call Thursday (May 4) about 9:30 am - Mrs. D was on the other end of the line -

• "I didn't send you anything, did I?" 
• "Why no," the confused me replied, "why would this worry you?"
• "I've got a virus!" the now-furious Mrs. D announces.

Some 28 hours after first bell (hell? Perhaps), I have got to admit that I still want to make some form of physical contact with the creator of this little piece of virtual hell and extract various chemicals and physically necessary organs from this person, preferably using a dull spoon and my bare fingers.

Without the editorializing, the facts (as they appear at 2-pm-ish on Friday) are these;

• Individual created a message with multiple virus payloads
• Virus payload one (VP1) activates upon opening the message
• "Opening the message" can also be done via the Outlook Preview Pane (so shut the thing off, will ya?).
• VP1 checks to see if the victim is using Outlook with Visual Scripting Host running on a PC
• VP1 replicates itself to EVERYONE in the victim's address book, delivering VP2
• Virus Payload 2 is another Visual Basic Script hidden in a text document
• VP2 infects the recipient's Windows OS and prepares for replication
• VP2 overwrites files with the extensions MP3 (compressed music) and JPG (JPeGs, or one of the more common forms of internet graphics).
• VP2 also replicates itself into any .VBS, .VBE, .JS, .JSE, .CSS, .WSH, .SCT or .HTA files , replacing the original content with a copy of itself.
• Downloads a copy of an EXE from 4 possible locations on the internet
• Uses the EXE to send your passwords file to somewhere on the internet
• Uses any other internet-enabled client (mIRC is one specifically mentioned) to spread itself around even further
• Generally wrecks havoc

Now, there's at least five variations of this thing, including one that says "Thanks for your order of the $326 diamond pendant for mother's day.  The attached document is a complete invoice.  If you have any question, please call the number provided in the invoice.  Thanks!"  Of COURSE you're going to open the damned attachment for something you didn't order...

Okay - breathe deeply and think positive, calming thoughts...

Much better.  Less a postal employee and more a technology professional.  Though I'm still working to blunt my spoon...  While this might not be the most prudent thing to do, the problem for this virus rests squarely on the heads of those fine folks who've delivered us yet another quality product - Microsoft.  I'm sorry, but when you're reduced to the level of "it's not our software, it's bad people using our software" it's a little like the murderer claiming it's not his fault the gun fired, the bullet did all the damage here.  Microsoft built the gun, loaded the gun, then sold it to hundreds of millions of people, world-wide.  Without even installing a safety device. Once VBS was installed, they could do all sorts of fantastic things with it - however, it is poor planning in the extreme, and bordering on corporate negligence and malfeasance, for a company to deliver a technology that is so completely and wholly pervertable that a mailbomb trojan virus can spread around the GLOBE in a little more than 6 HOURS. 

I think I'm beginning to see why the Justice department went after Microsoft.  It's not the monopoly, it's the monopoly that produces crappy software that upsets them.

On the other fronts; I'm researching other factors which will probably start popping up next week.  I've also got to get three computers finally configured and delivered to patiently waiting staff.  Have a good weekend, and open no e-mail before you've scanned it.