Take a deep breath. Count to 10, slowly. Envision a mountain stream with bears fishing, fishes bearing, John Denver strumming... OK, forget about John Denver. I've been fighting Microsoft worms for two weeks now, on every front imaginable. From rapid ACL construction in core switches to scripting the tracking of infected hosts in a large network to writing sendmail filters for MX relays, to implementing auto-sca Take a deep breath. Count to 10, slowly. Envision a mountain stream with bears fishing, fishes bearing, John Denver strumming… OK, forget about John Denver.I’ve been fighting Microsoft worms for two weeks now, on every front imaginable. From rapid ACL construction in core switches to scripting the tracking of infected hosts in a large network to writing sendmail filters for MX relays, to implementing auto-scanners and registration systems at colleges.I’m *(#&$%ing tired of it. My colo box has processed and discarded 76,306 SoBig.F emails in the past 8 days. Outrageous. The only silver lining is that I’ve done most of this with OSS tools, impressing more than a few Microsoft junkies. “We Have the Way Out” indeed.Tonight, I booted a lab box that hasn’t seen Windows 2000 in months. First thing I do is hit windowsupdate.microsoft.com to get the Blaster patch. I should have remembered where I stuck it locally, but I couldn’t, and it’s small.I then realized that this system had only been booted once before, and didn’t even have Win2K SP2. I ran that from my bulging Windows Update local cache, and the system rebooted. When it came back up, it was Blaster infected. Mind you, I only ran Windows update, bailed on that, and installed SP2. Craptacular.