Slashdot Mirror


Worm vs. Worm Battle Slows Networks

joel_archer writes "According this article at the DrudgeReport, a worm, apparently designed to patch MSBlaster infected Win2K and XP machines, brings various Canadian networks to a crawl. Hardest hit was the 411 system, Air Canada, and Ontario hydro electric operations. Apparently this is causing more problems than MSBlaster itself."

559 comments

  1. hmm, i wonder. by Pandora's+Vox · · Score: 5, Funny

    MS exploit virus comes out.

    mysterious patching virus starts making the rounds. massive consequences.

    we should be doing this more often, kids.

    -Leigh

    1. Re: hmm, i wonder. by Black+Parrot · · Score: 5, Funny


      > MS exploit virus comes out. mysterious patching virus starts making the rounds. massive consequences. we should be doing this more often, kids.

      Yeah, I'm working on a worm to kill off the worm that was supposed to fix Blaster, but I've been busy and haven't gotten it out yet. Look for it in your mailboxes tomorrow!

      --
      Sheesh, evil *and* a jerk. -- Jade
    2. Re: hmm, i wonder. by gfody · · Score: 4, Funny

      I'd better get started on my worm to kill your worm! er shit, semantec already has a definition file for anti.anti.anti.blaster.win32?!

      --

      bite my glorious golden ass.
    3. Re:hmm, i wonder. by Anonymous Coward · · Score: 0

      It could be Microsoft created it to protect itself, get rid of the worm, reinstate windowsupdate.com
      AND install SPYWARE and deactivate illegal copies of Windows :)

    4. Re: hmm, i wonder. by Anonymous Coward · · Score: 1, Funny

      the great northeastern blackout of '03 stopped my port of MSBlaster to linux (why should you have to run windows in order to DDOS microsoft update?)

      this anti anti anti worm craze is going to give me a second chance. if you know virus programming, i could use your help. download the source from gMSBlaster.sourceforge.net. the 0.0001a.alpha release just shows a nifty splash screen and prompts the user to install the worm as root (needed to get the proper permissions for raw acess to the networking stack), but doesn't actually do any denial of service or anything nefarious yet.

      please stop by and help out! this is soooo l33t!

    5. Re:hmm, i wonder. by Zro+Point+Two · · Score: 1

      Admittedly, I'm a Windows guy...but just think what this is doing for the reputation of Microsoft....and how much better Linux is looking for the companies servers...

      Why not desktops? well, I think it still has a way to go before the average user will be able to just sit down and work away, but not that much. However, they want things to be the same both at home and at work. SO, Linux needs to break into the homes. And for that to happen, it needs to be a little easier to set up, administer, and use. Therefore the major distro's (I'm thinking RedHat, Mandrake, Lindows, etc) may take a harder look at the home user for a short time period.

      Since trying to break into the office market at full force is still not working as well as anyone hoped, why not try starting at the home user? Break in there, maybe there'll be more people at least willing to use it at work (if not installing it on the computer without the admin knowing). Maybe that's the back door to get into the office market....but that's just my $0.0144 CDN.

      --
      Zro . two

      "I come from Canada...they say I'm slow....eh?"
    6. Re: hmm, i wonder. by Anonymous Coward · · Score: 2, Funny

      I believe the correct name for that would be the

      W32.Blaster.Buster.Buster.Buster.Worm

    7. Re:hmm, i wonder. by Stephen+Samuel · · Score: 1
      SO, Linux needs to break into the homes. And for that to happen, it needs to be a little easier to set up, administer, and use

      easy to set up and install will come when we've got more people getting Linux pre-installed as a standard.

      I've set up Linux for two room-mates now. I did the first one on a lark -- (installed a spare hard drive with RH 7.3 from my dead secondary box on it). a couple of weeks later I thought that he wasn't using it, but it turns out that he was using it, but he'd just been having almost zero problems with it.

      For my second room-mate, I set up RH8 and then added things like the MP3 mod for xmms and mplayer in place of xine (which seems to be non-functional). Oh yeah, I also installed the most recent version of gaim. I set it up after his MS Windows installation seemed to self-destruct on him (almost making the disk unreadable in the process). He's had very few problems since then, and most of them have been remote problems that he thought were the fault of Linux. I think it's been two months since he's asked me for help.

      Every once in a while I install all the update RPMS.

      for the most part, people's reluctance to use Windows has more to do with the fact that it's unfamiliar to them, and using Microsoft software has been traumatic enough that trying something 'experimental' has them scared shitless, than it has to do with any intrinsic problems with Linux.

      It's kind of ironic that the one thing keeping most people from moving from Windows is precisely that Windows is sooooo bad. (( Microsoft Windows: perpetually beta software for production systems ))

      --
      Free Software: Like love, it grows best when given away.
    8. Re:hmm, i wonder. by Mr.+Bad+Example · · Score: 4, Funny

      MS exploit virus comes out.
      mysterious patching virus starts making the rounds. massive consequences.
      we should be doing this more often, kids.


      That's the worst haiku I've ever seen.

    9. Re: hmm, i wonder. by kresmoi · · Score: 1

      >Yeah, I'm working on a worm to kill off the worm that was
      >supposed to fix Blaster, but I've been busy and haven't
      >gotten it out yet. Look for it in your mailboxes tomorrow!

      there was an old lady, who swallowed a fly...

    10. Re: hmm, i wonder. by flonker · · Score: 1

      I'll help you port it to Cygwin, once it's finished.

  2. But, but, but.. by Dh2000 · · Score: 1

    This is a GOOD worm!

    Okay, do you get it? These worms harm perhaps just as much as they help, in the short-term...

    1. Re:But, but, but.. by fussman · · Score: 2, Insightful
      A better worm would have done three things:

      1. Gain access via the same vulnerability. 2. Do something to block port 135 completely (without generating network traffic). 3. Go to the next vulnerable system.

      --
      Support Israeli punk bands. Man Alive.
    2. Re:But, but, but.. by RoLi · · Score: 2, Funny
      The funny thing is that many admins will react by reinstalling Windows from scratch.

      D'oh, d'oh indeed.

    3. Re:But, but, but.. by Jhon · · Score: 4, Insightful

      The funny thing is that many *nix admins (me included) would react to an exploited/owned machine the same way. Funny.

    4. Re:But, but, but.. by FuegoFuerte · · Score: 5, Insightful

      From what I've read, this worm actually does use the same vulnerability. And why block port 135 completely? Doing that risks breaking ish. Breaking ish isn't a good thing. No, here's what a better worm would've done:

      1) Once on a box, clean and patch said box.
      2) Sit and listen to port 135, waiting for Blaster to rear its ugly pulsing-zit-like head.
      3) In response to Blaster probe, install itself on Blaster-infested machine and start over at 1).
      4) On some set date in future, or when number of Blaster-probes remains 0 for a predetermined time (say 1 month), remove itself from system.

      By only loading itself onto machines which first probe it (trying to spread Blaster), it completely eliminates the stupid network scans. In that way, it only attempts contact with machines which have shown themselves to be Blaster-infested, while leaving the rest of the internet alone.

    5. Re:But, but, but.. by Anonymous Coward · · Score: 1, Funny

      Didn't you mean:
      1) Once on a box, clean and patch said box.
      2) Sit and listen to port 135, waiting for Blaster to rear its ugly pulsing-zit-like head.
      3) In response to Blaster probe, install itself on Blaster-infested machine and start over at 1).
      4) On some set date in future, or when number of Blaster-probes remains 0 for a predetermined time (say 1 month), remove itself from system.
      5) ???
      6) Profit!

    6. Re:But, but, but.. by BlackHawk-666 · · Score: 2, Informative
      That's because it's the safest approach...unless of course you are running tripwire and can track the changes to your system. Besides, you can simply quarantine off your data, re-install your standard base, then drop the data back in onto a machine that now has a known build of software. Of course, this wouldn't be particularly safe when data and code are mixed together, like in files from a certain word processor we all know and hate (MS Word).

      I actually rebuilt my server the other day onto a new machine, not because of a worm, but because I got a second hand dual proc 750mzhz server (with RAID 5!) for nothing. It was pretty east to install the base system, RedHat 9, run up2date, then copy the important files from /etc into place. Back up and running in no time. Try doing that with the registry.

      --
      All those moments will be lost in time, like tears in rain.
    7. Re:But, but, but.. by timmyf2371 · · Score: 4, Insightful
      Whether a worm is good or bad, you still don't want it executing on your box without permission, IMO.

      Perhaps have a stage in there where the "Good Samaritan" worm pop up and explain to the user how it got there, the implications of the security issue, and ask the user if they want to fix their system.

      --

      Backup not found: (A)bort (R)etry (P)anic
    8. Re:But, but, but.. by goatan · · Score: 0
      don't say MS is doing something bad here, they are doing a wonderful wonderful thing;

      M$ didn't have anything to do with the worms exept for there sloppy codeing allowing them to happen

      --
      Saying Apple is better than MS is like saying Botulism is better than rabies.

    9. Re:But, but, but.. by Jhon · · Score: 1

      I've migrated from various flavors of Win servers (NT (old and new), 2k) and various flavors of linux -- both for work and home. I completely agree. Hands down, moving from one machine to another using in linux takes me about a 10th of the time.

      Even database migration has been easy. Can't say that for the win environment. I had a nightmare moving one client from interbase on NT4 to MS SQL2k on win2k.

      BUT, I work with what I'm given.

    10. Re:But, but, but.. by machine+of+god · · Score: 1

      I'm sure they'll suggest that at the design review next time they're about to write a worm.

    11. Re:But, but, but.. by Anonymous Coward · · Score: 0

      Even database migration has been easy. Can't say that for the win environment. I had a nightmare moving one client from interbase on NT4 to MS SQL2k on win2k.

      What a wonderful comparison, taking data from one database system running on one OS to another database system running on another OS. Gee, I wonder why it took you so long, you fucking Linux troll.

    12. Re:But, but, but.. by adagioforstrings · · Score: 1

      This could be wrong, but I would guess (I haven't tried it) that a Windows program couldn't bind itself to port 135 to listen since it's the RPC port and the system is already listening there!

    13. Re:But, but, but.. by Stephen+Samuel · · Score: 1
      3) In response to Blaster probe, install itself on Blaster-infested machine and start over at 1).

      I think you'd want to include some sort of mutex to make sure that only one copt of the program runs on a box. Once the program gets anywhere near common,, I'd expect that any box running the originaal worm would get hundreds (if not thousands) of counter-attacks.

      On a tangent, I've got a script that allows me to use my firewall logs to auto-generate warning emails to the responsible ISP of the attacking system, After that thing was running for half an hour, I realized that I was effectively mail-bombing my ISP. sigh....

      Happily, they haven't cut off my account.

      --
      Free Software: Like love, it grows best when given away.
    14. Re:But, but, but.. by Findel · · Score: 1

      No what it should do is 1. Delete MSBlaster.exe 2. then create a dummy file with the same name in its place 3. set write permissions to the NEW MSBlaster.exe so that Blaster can not re-install. Easy Peasy. Or at least thats what someone tried to tell me to do. So why cant a worm do it. it just MUST work, the PC Support guy told me (Detect hint of sarcasm). Though the idea is good-ish.

      --
      "I love deadlines. I like the whooshing sound they make as they fly by."
    15. Re:But, but, but.. by Anonymous Coward · · Score: 0

      you can't honestly think that a malicious virus of the same appearence wouldn't pop up in minutes.

    16. Re:But, but, but.. by aprosumer.slashdot · · Score: 1

      Port 135 is used at least by MS Exchange Server. Blocking 135 internally (behind the firewall) would not necessarily be a good thing if the organization uses Exchange Server to handle messaging (e-mail), contacts, address book, and calender for all its Users. Blocking ports really depends on what type of network services are allowed and used by the organization.

      If the W32.Welchia.Worm was meant as a "good worm" by the writer, then the emergent DOS behavior of the W32.Welchia.Worm obviously shows that the writer has a complete lack of sophistication and critical judgment.

    17. Re:But, but, but.. by Jhon · · Score: 1
      What a wonderful comparison, taking data from one database system running on one OS to another database system running on another OS. Gee, I wonder why it took you so long, you fucking Linux troll.
      You're kidding right? I've moved databases from different RDBs running an various flavors of *nix to different RDBs running different flavors of *nix and it has historically been quite smooth (although, I had some problems with an older SCO system). I've even moved from unix to win32 and the other way.

      My experience has been that anything relating to win32 and RDBs is far more time consuming.

      Linux troll indeed.
    18. Re:But, but, but.. by Anonymous Coward · · Score: 0

      natalie portman does that

    19. Re:But, but, but.. by betong · · Score: 1
      In the dawn of the internet, benevolent worms were far more common than the nasties we see today. To quote from Julian Assange's book 'Underground':

      "Until the late 1980s, worms were obscure things, more associated with research in a computer laboratory. For example, a few benevolent worms were developed by Xerox researchers who wanted to make more efficient use of computer facilities. They developed a `town crier worm' which moved through a network sending out important announcements. Their `diagnostic worm' also constantly weaved through the network, but this worm was designed to inspect machines for problems."

      --
      . ~/.sig
  3. Hm... by gooru · · Score: 3, Insightful

    So, the question I have is: do you think he was trying to be a good Samaritan and just wrote something that caused serious problems, or do you think he purposely wrote something that would cause problems but would spread wild due to the ostensible good it was trying to do?

    1. Re:Hm... by zcat_NZ · · Score: 5, Insightful

      Personally, I'd have written a worm that enables automatic updates and XP's inbuilt firewall. If windowsupdate can't handle the load perhaps they shouldn't have designed it in a way that -purposely breaks- normal web caching.

      The current round of worms are clumsy and unimaginitive. I think it's only a matter of time before we see a worm that does some -real- damage.

      --
      455fe10422ca29c4933f95052b792ab2
    2. Re:Hm... by billimad · · Score: 2, Insightful

      I'm more concerned that this might be the start of another hackers war - the consequences of this turf war playing out in a much larger (and vunerable) playing field already seem evident.

    3. Re:Hm... by CurlyG · · Score: 1
      In English, we say built in. :)

      ...unless we have a more comprehensive vocabulary, in which case we may choose to say inbuilt

      --
      You know they call 'em fingers but I've never seen 'em fing. Oh, there they go.
    4. Re:Hm... by p3d0 · · Score: 1
      The current round of worms are clumsy and unimaginitive. I think it's only a matter of time before we see a worm that does some -real- damage.
      What do you mean? I think DDOSing windows update is pretty clever, and I think it did some -real- damage. What more do you want?
      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    5. Re:Hm... by zeugma-amp · · Score: 1

      What more do we want? Well for starters, all of the recent worms have been fairly benign in what they do. They attempt to spread, which causes network disruptions, and turn the infected computer into a zombie. The blaster worm also unneccesarily caused systems reboots that alerted the user to infection. If the worm needed the reboot to install some service, it should have just waited until one of the thrice daily reboots that are normal for windows computers. If they'd really wanted to be nasty, the worms could have fdisk'ed the users harddrive after successfully infecting 5 other systems, with a 48 hour timer in case it wasn't able to spread itself.

      Windows users have been extremely lucky in that these worms have been relatively benign compared to what they could have done. I hope their luck eventually runs out. I think a serious worm/virus that effectively kills the host is the only thing that will really wake people up to what kind of crap they are running, and the risks they are taking for running windows.

      --
      This is an ex-parrot!
    6. Re:Hm... by ntsucks · · Score: 2, Insightful

      I agree. For all the talk of damage and problems, to date most worms have been what I would consider mostly harmless because they can be removed and the hole patched. Wait until one comes along with a "format c:\" on a little time delay. Or maybe look for important files like databases and start randomly corrupting them.

      We have not yet seen a truely damaging worm. If a few reboots and some network congestion can cause this many problems, a truely destructive virus could probably cause worldwide economic turmoil.

      --
      Those who can do. Those who can't sue.
    7. Re:Hm... by ratsnapple+tea · · Score: 0

      Or maybe look for important files like databases and start randomly corrupting them.

      Corrupting them? How about mailing them to everyone in the address book? You'd have credit card numbers, confidential company documents, all kinds of things flying around the internet. The legal implications would be staggering, the economic damage enormous. It's only a matter of time before someone writes a worm like this.

      yours

    8. Re:Hm... by pjrc · · Score: 1
      Personally, I'd have written a worm that enables automatic updates and XP's inbuilt firewall.

      That would conflict with the REAL payload of this worm, which is to install a TFTP-based backdoor on every computer it infects. Sure, it patches the original hole, but the author hardly had the computer owner's best interests in mind!

    9. Re:Hm... by danila · · Score: 1

      Surely you are aware that this very thing already happened with the past worms that sent random files as attachments, aren't you?

      P.S. There is too much subtlety on Slashdot.

      --
      Future Wiki -- If you don't think about the future, you cannot have one.
    10. Re:Hm... by p3d0 · · Score: 1

      True enough. I think DDOSing Windows Update was clever, but you have a point that it didn't actually damage infected hosts.

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    11. Re:Hm... by MasterSLATE · · Score: 1

      Touche! Thanks for expanding my knowledge

      --

      [sig]www.masterslate.org[/sig]
  4. This is exactly why by Magic+Thread · · Score: 4, Informative

    "cleanup" worms are still bad. Since the original worm didn't do anything except attack a domain name that's no longer in use, the cleanup one may even be worse.

    1. Re:This is exactly why by Anonymous Coward · · Score: 0

      oh yeah, and of course all of those normal computer users will know how to protect their computers from the original worm... good idea, MS is evil.

    2. Re:This is exactly why by Keeper · · Score: 1

      Right, because we all know that nobody else will write one that is worse than the previous one...

    3. Re:This is exactly why by admbws · · Score: 5, Insightful

      It's a case of a lesser of two evils. The problem is, there are thousands of exploitable boxes and if nothing is done about it, in the long term, this is going to cause some serious problems. Many of the owners of these systems will never fix or patch them themselves.

      It's really a toss-up between a worm that temporarily slows down networks by spreading and patching the systems it infects, then automatically deleting itself after a set date, or a script kiddie scanning the entire internet, picking up these boxes and adding them to his DDoS network, which can slow down all or any network(s) (root DNS servers, anyone?) he or she chooses at a later date.

      It is for this reason, IMHO, that these exploitable boxes are a threat to the integrity of the internet, and while writing a worm to automatically patch the systems might be rather militant, something has to be done about it.

    4. Re:This is exactly why by RallyNick · · Score: 1

      the "good" worm does much more than cleaning up blaster, it actually patches the whole on computers with ignorant owners so some kid can't use it again for his trojans.

    5. Re:This is exactly why by natmsincome.com · · Score: 1

      It also turned off computers so you couldn't connect to the internet.

    6. Re:This is exactly why by zangdesign · · Score: 4, Insightful

      writing a worm to automatically patch the systems might be rather militant, something has to be done about it.

      Yes, and the proper thing to do would be to contact the system administrator and let him/her know that their system is vulnerable. Releasing another worm to patch the first worm is just as morally wrong and illegal, since it is entering the system by unauthorized means.

      Two wrongs do not make a right. Frankly, I hope they find both the guys that wrote those damnable things and throw them both in jail.

      The moral of this story is: keep your damn hands off something that ain't yours.

      --
      To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
    7. Re:This is exactly why by Anonymous Coward · · Score: 0

      No longer in use? Windowsupdate.com is very much in use, unfortunately it has been put temporarily offline, so people who need to patch their system against the worm, can't get to it the patch.

      The people who can't remember longer names, are the same people who would never find the right place to click in control panel, and who don't update their system until absolutely necessary.

    8. Re:This is exactly why by Kibo · · Score: 1

      Naw, they are different evils. One was malicious, and the other arrogant. Excecute the first guy, and cane the second.

      --
      --Jimmy has fancy plans; and pants to match.
    9. Re:This is exactly why by sperling · · Score: 4, Insightful

      This worm is just as bad, maybe even worse than the first.

      Script kiddies are in fact way safer now than before this good samaritan, since most of the lazy users that have been compromised also by other means than the initial worm now will think everything's fine and leave the additional rootkit installed and running. If this second worm hadn't made things appear normal again, these users would have to reinstall their systems and thus get rid of e.g. the IRC drones that currently annoys most of the major IRC networks, including the one I admin a server on.

      In addition, this worm wastes bandwidth on somewhat responsible users that do not trust something using an exploit for gaining access to keep their systems secure. Would you leave your box as is if this worm had "secured" you? Or would you be worried and prefer to reinstall and manually patch?

      However good the intentions of this worm might be, it's just adding to the problem.

      --
      The next great MMORPG.
    10. Re:This is exactly why by 26199 · · Score: 3, Informative

      Er... which system administrator would that be?

      I get the impression the vast majority of systems that are still at risk belong to good old incompetent (through no fault of their own) home users. Contact and explain?... not likely to be very effective.

    11. Re:This is exactly why by kinnell · · Score: 1

      I'm prepared to bet that the person who wrote the cleanup worm was more interested in writing a clever worm than cleaning up peoples computers. If this were the case, the fact that he chose to do something constructive with his skills has to be a good thing, in a lesser-of-two-evils sense.

      --
      If I seem short sighted, it is because I stand on the shoulders of midgets
    12. Re:This is exactly why by songbo · · Score: 1

      Maybe what this is just the second round of attack by the Blaster writers. Use the worm to bring down more systems. Intention? Bring down as many M'soft systems as possible. Who knows, there may even be a virus writing competition out there, and they're trying to see who can infect the most systems. :)

      --
      There are 10 kinds of people in the world - those that know binary, and those that don't.
    13. Re:This is exactly why by Anonymous Coward · · Score: 3, Informative

      Let me say up front that the IT department at my company is not at all on top of things like massive exploits. The company LAN has suffered the wrath of Nimda (for several days because IT neglected to tell people to shut down Everyone shares), Code Red, and now MSBlast and MSBlast.D.

      However, I'm our one man Hosting and Deployment department for our web-based apps, so I am pretty diligent about this stuff.

      About a week after MS released the RPC patch, I had it tested and on all the servers used to deliver our products. And, since I don't trust our IT department, I run Tiny Personal Firewall on my own workstation so I can see when somebody is coming after my machine.

      We weathered MSBlast pretty well - I detected it fairly early with TPF and was able to get the infected people around me cleaned up quickly. Luckily, all the servers under my control were already patched, so our client-facing stuff was safe.

      Then, yesterday, MSBlast.D ripped through the company. It was apparent that a number of people hadn't patched when the original Blast came through and that IT didn't do anything as basic as a LAN/WAN wide scan for vulnerable boxes. Again, I wasn't worried about my machines, so much, but MSBlast.D brought our network to a standstill where the original Blast was just a minor nuisance.

      With the LAN nearly dead, I couldn't get to any of the remotely hosted servers for which I am responsible. Our server monitoring software had similar problems and was alarming all day.

      Now, I understand that the true fault behind this lies with the IT department for not at all being on the ball about this, but I'm also a bit pissed with the person who thought it a good idea to become a sort of vigilante patcher and create a worm that essentially resulted in a LAN-wide ping flood DoS. The original MSBlast was amusing to me because it was so easy to get rid of. MSBlast.D, however, was infuriating because it affected even machines that were properly secured/patched by bogging down the network.

    14. Re:This is exactly why by p3d0 · · Score: 1

      I disagree. If the numbnuts at Air Canada had updated their systems against Blaster, this wouldn't have been a problem.

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    15. Re:This is exactly why by Shardis · · Score: 1

      +5 Insightful? The poster and whoever modded 'em obviously knows nothing about what's going on.

      The damn cleanup worm's auto-terminate date is Jan 1, 2004.

      Lesser of two evils? Do you know how every bit of code executes on any given customized system? If not, you probably shouldn't be illegally penetrating systems to run code on them should you? Idiot. This is all virus writers are doing, just by proxy.

      Whoever wrote this supposedly "beneficial" worm should get as much jail time as the orgional virus writer, if not more for being such a arrogant moron.

    16. Re:This is exactly why by Anonymous Coward · · Score: 0

      The real problem with this work is that it's very poorly written, like the first Blaster. It shouldn't be scanning like this. Maybe if it only scanned once, but not again and again. There are a whole lot of different ways it could have patched the systems, and not caused this problem.

    17. Re:This is exactly why by Kyle+M · · Score: 1

      This is completely wrong. The affected machines are part of a private network so the risk is limited to internal attacks. Company firewalls protect both the internet and the inside users: hackers can't exploit the machines, and users can't reach the internet on restricted TCP ports. And most corporate firewalls restrict ALL traffic with http going to secured proxy servers.

    18. Re:This is exactly why by coffee_admin · · Score: 1
      "No longer in use? Windowsupdate.com is very much in use, unfortunately it has been put temporarily offline, so people who need to patch their system against the worm, can't get to it the patch."
      I suppose the Windows Update link the Start menu or in the Tools menu of Internet Explorer is to complex for the average Joe.
      --
      Prozac makes the voices in my head say nice things to me.
    19. Re:This is exactly why by hendridm · · Score: 1

      > Yes, and the proper thing to do would be to contact the system administrator and let him/her know that their system is vulnerable.

      Riiiiight. Would you like a printout of my Apache logs for the last few years with references to Code Red and friends grepped for your tracking pleasure?

    20. Re:This is exactly why by Abcd1234 · · Score: 1

      No, this is why a badly written cleanup worm is bad. Had the original author designed the worm differently (for example, making it reactive rather than proactive), it wouldn't be causing these problems now. Unfortunately, they apparently didn't have the understanding or the forethought to realize this.

      'course, I still feel there are real *ethical* considerations to be made, but from a purely technical standpoint, IMHO, it *is* possible to create a safe cleanup worm.

    21. Re:This is exactly why by sweet+'n+sour · · Score: 1

      Lets remember a couple of things here:
      A. It's not our responsibility to notify anyone of anything. If the dope hasn't patched his system by now, he's not going to. Besides, have you seen just how many hits servers are getting in a day? Have you been taking the time to lookup and call each infected system that has tried to infect yours? I doubt it.
      B. It IS our responsibility to keep our own server running well. If this mean going on the offensive, then so be it.
      This is simply another public nuisance combined with neglect situation that we see so often in the real world. From children being taken away from neglecting parents to people not mowing their lawns, the public has a history of taking control of a situation when the owner does not.

      Simply put, if you neglect your servers, you will loose control of them... Either by hacker, or perhaps your isp.

    22. Re:This is exactly why by Kallahar · · Score: 1

      Using Tiny actually puts you more at risk: PFExploit.c due to a buffer overflow bug. Tiny is no longer issuing updates, but they gave/sold the source code to Kerio who is now offering the same product (same source code) with patches with Kerio Personal Firewall

      Also remember that the strength of your personal firewall is only as good as the rules you set. You can easily open your computer by accidentally allowing too much traffic through.

    23. Re:This is exactly why by Batzerto · · Score: 1

      This shows a major flaw in the cleanup worm. It should just sit idle until an infected machine tries to contact (infect) it, then spread itself to that machine and clean it up. This would reduce the traffic caused by the cleanup worm to a minimum.

    24. Re:This is exactly why by Anonymous Coward · · Score: 0

      During the earlier days of the infection, when people were scrambling to upgrade their systems, spam volume dropped off significantly (At least until the SoBig.F virus got released in the wild).

      We were speculation the reason for the dropoff was that when people upgraded their PC''s, they also eradicated the Spam trojans, and is probably the reason why the new SoBig.F was released in the wild.

      Thankfully, the SoBig.f was spread by people's stupidity when they opened up attachments.... People will NEVER learn...

      Now, when we report spam we also give the ISP important information to tell their users how to get rid of it, but with a recommendation they work with the infected user to setup a "sting", so when the spammer connects to the infected machine, they can be traced.

      By port scanning the infected machine, looking for port 606 (it may have changed now), would reveal a trojan is "listening" and ready to proxy the spam.

      If I wasn't a law abiding citizen, I would "sneak in" the machine and install a program to Email me when the spammer logs in, with all the gory details on where they came in from, and nail the bastard.

      ISP's can then put an IDS online (many snort rules are already available). But (sigh) ISP's are often clueless, and have all sorts of privacy issues they have to deal with...

      arghhh! and the massive spam effort continues un-checked... but you just wait, this is just the tip of the iceberg as this SoBig.F is slowly sneaking into people's WinBlows systems...

      I wonder what percentage of spam reduction we would have if all the WinBlows boxen would just vanish... Yea I know.... DREAM ON!!!

    25. Re:This is exactly why by zangdesign · · Score: 1

      I agree that it is your responsibility to maintain your own servers. However, it is not your responsibility to go tromping into someone else's system under any circumstances without prior authorization.

      I believe you are viewing the internet in the same way that we view a park or other real-world public space, and there is no comparison. The internet is not the real world and never will be.

      --
      To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
    26. Re:This is exactly why by sootman · · Score: 1

      Yes, and the proper thing to do would be to contact the system administrator and let him/her know that their system is vulnerable.

      And how, exactly, do you contact the sysadmin for J. Random User's dialup-connected computer? Personally, I'm all for the worm-fixing-worm. Not perfect, more of a lesser-of-two-evils kind of thing. Vigilante justice is better than no justice at all. And remember, the only difference between vigilante justice and regular justice is the government condones one but not the other.* Both dole out punishment, both are fallable, both are better than nothing at all.

      * Specifically, the US government. I'm sure there are plenty of places where what we consider vigilante justice is A-OK, and they'd be all for this worm-killing-worm. And isn't cyberspace a) international and b) a place in its own right?

      The moral of this story is: keep your damn hands off something that ain't yours.

      But what if someone, by their inaction, is damaging the Internet for the rest of us? They have the right to waltz onto the Internet, unprotected, becoming conduits for worms, and we aren't allowed to do anything? Remember, the Internet is very different from the real world in many ways. I can copy a file from my computer to yours. You now have a 100% perfect duplicate, yet I have lost nothing whatsoever. Copyright laws, property laws, etc. weren't written with this in mind. If someone steals your car and uses it to crash into other cars, you'll know. If someone hacks into your computer and uses it to attack other computers, you won't. Again, laws, rules, and customs from the physical world are not a perfect match. I'm not saying I have all the answers, but I do know that you can't just take a rule from the physical world and say "This is the rule, follow it here." "Keep your damn hands off something that ain't yours."? What if someone is causing you to put your hands on something that is mine and you're unaware of it? What do we do now? The old rules do not apply.

      --
      Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
    27. Re:This is exactly why by dasuridai · · Score: 1

      The issue of lazy / nonexistant admins is difficult to balance with the potential for DDoS attacks. I think an adequate compromise would be to email the address 1 week in advance of delivery of a self-patching worm. Therefore, if the system has been patched in that time, the worm-patch will not be able to operate because the system has already been fixed.

    28. Re:This is exactly why by Anonymous Coward · · Score: 0

      Two wrongs do not make a right.

      No, but ... 2 lefts will!

    29. Re:This is exactly why by zangdesign · · Score: 1

      The old rules do not apply.

      Oh, I'm sorry, how silly of me. The new rule is apparently "The ends justify the means".

      How very Democrat of me to assume otherwise.

      --
      To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
  5. yes by LBArrettAnderson · · Score: 1

    of course it's causing more problems, because it's PREVENTING MSBlaster from causing the problems in the first place. any slowage at all would be considered more of a problem than no virus at all.

    1. Re:yes by fussman · · Score: 0

      just make a worm that blocks port 135 on all XP/2k systems and you'll be better

      --
      Support Israeli punk bands. Man Alive.
  6. I think I'll take the bus by evn · · Score: 3, Interesting

    Flying is hard enough - they tell you it's the safest way to travel. Now we find out it's run by a system famed for it's ability to crash?!

    The service is so bad; the management was so bad. The system is just a mess, just a mess. I had my luggage delivered to Toronto, I was told on Saturday, so I don't have anything.

    Seriously though, that sounds more like the airline's standard crumby service than the latest Microsoft worm/virus is to blame.

    1. Re:I think I'll take the bus by ripicheep · · Score: 1

      I did take the bus that day in Toronto and I know that some of the massive air canada delays were due to a major reduction in staff that just happened without any real sheduling change.

      OT: During the power outage when the airports and train stations were not operating, the greyhound terminals with their diesel storage and generators were running on time.

      --
      "A witty saying proves nothing." -Voltaire
    2. Re:I think I'll take the bus by Anonymous Coward · · Score: 0

      To your information, flying is not the safest way to travel.
      Let me explain that.
      safety1=(number of people killed+number of injuries)/sum kilometer travelled
      safety2=(number of people killed+number of injuries)/sum hours travelled

      Safety1 is the lowest by flying. Safety2 is the highest.

    3. Re:I think I'll take the bus by IsoRashi · · Score: 1

      Flying is hard enough - they tell you it's the safest way to travel. Now we find out it's run by a system famed for it's ability to crash?!

      They haven't said anything about the systems that support the NAS. HOST doesn't run on anything remotely like Windows or even Linux. I don't know how best to describe it--it's its own OS and application all in one. I don't have a link to any sort of statistics, but I've heard that your chances of dying in a plane crash are less than getting into a fatal car accident. But that doesn't scare me away from driving.

      Anyway, I have worked pretty closely with air-traffic controllers and these people are simply amazing. They go through a lot of sector-specific training before they're allowed to sit at a position by themselves and most of them are pretty smart to start. You have the occasional controller who isn't too bright, but I assure you he/she is still qualified for his job.

      --
      This is not the greatest sig in the world, no. This is just a tribute.
  7. Re:So? by joeykiller · · Score: 5, Interesting

    Who cares?

    Well, according to an article I read yesterday the MSBlast theory of the power blackout in the US and Canada isn't dead just yet. They don't think MSBlast was the reason of the blackout anymore, but that the worm slowed down and crashed monitoring systems. In that way the worm worsened the problem and didn't stop it where it could have been stopped.

    If this theory is right I guess 50 million americans without power cares whether incompetent admins can't keep their networks up.

  8. Another article... by Dark+Nexus · · Score: 5, Interesting

    The Register also has an article on this.

    Basically the same core facts, but also talks about the ethical issues with "good" worms.

    --
    Dark Nexus
    "Sanity is calming, but madness is more interesting."
    1. Re:Another article... by bar-agent · · Score: 1

      The Register? Ethics? Something is not computing...

      --
      i'd hit it so hard, if you pulled me out you'd be the king of britain [bash.org]
  9. Ultimately... by metatruk · · Score: 4, Interesting

    ISPs are going to start firewalling off more and more ports because of the fact that Windows is insecure. But more importantly, customers don't care enough about the problems to deal with their own responsiblity: securing their own machines.

    Many ISPs already filter the standard windows NetBIOS ports (137-139, i think) because of possible attacks.

    I think this opens an interesting problem. If people don't start taking their own computer's security seriously, other people will be forced to -- their ISPs. Will ISPs become liable then if attacks do take place?

    1. Re:Ultimately... by zakezuke · · Score: 1

      Actually, I think that these ports are filtered due to the fact that people had open file shares.

      When broadband was new, and hit offices and small networks, it wasn't all that unusual to hit your network neighborhood and see, well, your neighbors.

      I could be wrong on this, but I know this was an issue circa 1999/2000.

      --
      There is no sanctuary. There is no sanctuary. SHUT UP! There is no shut up. There is no shut up.
    2. Re:Ultimately... by Anonymous Coward · · Score: 0

      Port blocks are stupid. Apps will follow the lead of instant messenging software and tunnel through various "unblockable" protocols/ports. This makes protocols more complicated and thus error-prone, with obvious implications for security. The Microsoft protocols are a perfect example for the mess this creates: there are half a dozen SMB related ports, all capable of roughly the same set of features (but not exactly the same). It's a multiple ports to multiple applications rats nest.

    3. Re:Ultimately... by Tim+C · · Score: 5, Insightful

      Many ISPs already filter the standard windows NetBIOS ports (137-139, i think) because of possible attacks.

      I see that as a good thing. What possible reason is there to have file and printer sharing open to the internet?

      True, it shouldn't be the responsibility of the ISP, and no, I'm not exactly happy with the thought of port filtering becoming common place and extending to other ports (ftp, ssh, http, etc - after all, "it's a home connection, you shouldn't be running servers..."). As an interim measure, though, it at least does help to contain the problem.

      If people don't start taking their own computer's security seriously

      I think you have that wrong. People do take their computer's security seriously, they just don't know enough about it. They also, largely, expect to be able to just switch their computer on, and have it work, like everything else they use. TV, video, dvd, microwave, car, central heating - they're all made, installed or set up once, and then just work. If they break down, they're replaced, or a qualified engineer is called to fix them.

      People aren't yet used to the idea that computers don't quite act like that. You and I may have been working closely with them for years, but most "ordinary" people haven't. So, they expect them to require the same amount of effort as everything else they use.

      I think that PC manufacturers could go a long way to helping here - shipping with firewalls and virus scanners preinstalled and configured. Perhaps have a couple of big, impossible to miss buttons on the desktop - "click here if this machine is connecting directly to the internet", "click here if this machine will not connect to the internet, or will connect via another machine on the network", "click here if you don't know what that means", that configures the machine appropriately for its role. That way, the gateway can be secured, while the rest of the network can share files and printers. No, that's not a foolproof plan, but I think it would go a long way to helping solve the problem.

      Don't just bitch and moan at the "clueless, irresponsible" users - teach them to know better, and help them while they're learning.

    4. Re:Ultimately... by iamacat · · Score: 5, Insightful

      Surely operating systems should be very secure by default, as in not accepting ANY incoming connections, no ActiveX, no executable e-mail attachments. One shouldn't have to install security patches every week just to read e-mail and browse the web.

      What we have here is one company's lack of responsibility and desire to make a quick buck without working on software quality. Its so fortunate they don't make cars.

    5. Re:Ultimately... by ameoba · · Score: 1
      Well, I assume most ISPs have clauses in their contracts like mine


      Customer uses $ISP's service at his/her own risk. $ISP does not guarantee the safety, security or integrity of any data and is not liable for any damages done to person or property as a result of any data acquired from or through or stored at the facilities of $ISP or involving $ISP's service in any way.
      --
      my sig's at the bottom of the page.
    6. Re:Ultimately... by lightcycle · · Score: 3, Insightful

      I don't think that impossible to miss buttons will help at all. People will click them and be none the wiser what they really do behind the scenes.
      What people need to realise is that a computer is not like their microwave or tv. A computer doesn't come with all those limits in what they can do. Therefore, a computer must also be more complicated to use.
      Somehow, people that buy a computer must realise that it won't plug and play. They will have to read some documentation (Which should be supplied by the manufacturer, and be easy to understand). If people only realised that to operate a computer they need to clue themselves in slightly, and if computer manufacturers understood the importance of good documentation we would soon see less clueless users.

      --

      The stars that shine and the stars that shrink
      in the face of stagnation the water runs before your eyes
    7. Re:Ultimately... by Anonymous Coward · · Score: 0

      It should be possible to buy fool-proof "email-machines" and "web-displays". These kind of systems have no excuse for not being secure, except their users who want them to be more than they can be securely.

    8. Re:Ultimately... by muirhead · · Score: 2, Insightful
      What people need to realise is that a computer is not like their microwave or tv. A computer doesn't come with all those limits in what they can do. Therefore, a computer must also be more complicated to use.

      I have to mainly agree with you. Although I believe that most people want their computer to be more like a tv. Convergence will eventually turn the PC into an appliance.

    9. Re:Ultimately... by hdw · · Score: 3, Insightful
      This is a discussion that I think most ISPs have had for many many years.

      Blocking dangerous ports would be a good thing for most ISPs, they want subscribers and online time, but preferrably as little traffic as possible.
      Even more so as broadband/always-on connections multiply.

      But all forms of ISP controlled blocks create two problems.

      Some people want those ports open, some because they use those ports, some because they se it as an invasion of privacy (it's _my_ port, and _my_ computer, _I_ decide if I want it blocked or not!).

      As soon as the ISP start to take 'responsibility' is hard to say where that responsibility ends. "You block port xxx but not port yyy, and because of that 1000's of customers got infected, bad ISP!"
      And of course, it does mean more work for the staff, which costs money for the ISP.
      But it's not a simple issue.
      Most of it also applies to ISP spam blocks.

      --
      Executive Pope (small) Kallisti Engineering
    10. Re:Ultimately... by Lumpy · · Score: 1

      I firewall ALL ports that are not needed by myself... default firewall was all ports closed. I had to open those I wanted open.

      and anyone connected to the net not doing the same is an idiot.

      PLain and simple.

      They dont let you drive on the highways without training and a license... Why the hell do we let people on the internet without any fricking idea where the steering wheel is?

      --
      Do not look at laser with remaining good eye.
    11. Re:Ultimately... by shadowcabbit · · Score: 1

      In my experience, no one will ever press the button marked "click here if you don't know what that means" until they call tech support and are told the correct button to press, which they will ignore. People do not take well to being called stupid-- they will freely admit it themselves, usually as a defense mechanism when they fail to follow simple directions ("I thought you said 'press delete', not 'don't press delete'-- I'm no good with these things")-- but if a button is labeled "click here if you don't know what you're doing" it will never, ever be pressed.

      --
      "Why Subscribe?" Good question...
    12. Re:Ultimately... by ostiguy · · Score: 1

      Here is my semi on topic premise:

      People don't spend enough money on their computing environment. Joe consumer wants the cheapest solution available, that mainly works. For cars, people expect to pay over 1k a year in gas, a couple oil changes, etc. If Joe Consumer spent 50 bucks a year to buy a security product for the latest woe (firewall, spam, antivirus), they really wouldn't have any problems. If MS has engineered win95 to do all these things way back in the early 90s, or if they went with a subscription model promising to take care of unforseen security problems, it would have cost Joe Consumer considerably more. Joe Consumer wants to be able to download music for free, but doesn't want to pay the piper when he downloads a bogus mp3 that is trojan infected, or some such.

      ostiguy

    13. Re:Ultimately... by Gothmolly · · Score: 2, Interesting

      What possible reason is there to have file and printer sharing open to the internet?
      Because I want to.
      Because I can.
      Because it's easier than trying to nail up some IPSEC tunnel between my Win box and someone else's.
      ISPs ARE and SHOULD not become content producers, providers, or censors. It's connectivity, that's all. Otherwise, when do you stop?

      --
      I want to delete my account but Slashdot doesn't allow it.
    14. Re:Ultimately... by azzy · · Score: 1

      I don't have a steering wheel on my computer. And when I surf the web while drunk there's no chance I'll run someone over and kill them. But by all means, lobby your politicians to make laws stopping you from doing /anything/ without a license, they'll probably be keen on the idea.

    15. Re:Ultimately... by Shardis · · Score: 2, Interesting

      "I see that as a good thing. What possible reason is there to have file and printer sharing open to the internet?"

      Arg, thinking like this just irritates the hell out of me. Get this through your head please. It's MY computer, I'll do whatever the hell I want with it. If I'm breaking laws or causing a problem for you, THEN you may actually be an interested party. Don't we already have enough damn inane laws/regulation to protect us from ourselves?

      Delegating the responsibility for controlling a machine that could pontentially affect others to the owner isn't too much to ask, is it? Hell, we do it everything else!

      "Gee, I didn't realize that if my brakes didn't work I could run someone over with my car..."

      Yeah, educating the users is a good thing. But they should already have some common sense.

      I always tend to shock others when I say that home users should be eligable for criminal (not civil) fines for their (usually intentional) ignorance. I'll gladly pay taxes to hire some actually competant "internet cops" to weed out US problems and act for the US for international problems.

      I'm very much into freedom of speech and various civil liberties, but c'mon, let's have some common sense and realize that what we do affects others...

    16. Re:Ultimately... by Squash · · Score: 2, Insightful

      Unfortunately, you can't look at it that way in the real world. An ISP's responsibility to provide connectivity is its highest priority. They don't care about Blaster Joe or Typhoid Annie, and shouldn't be expected to put up any safeguards against them spreading thier joy. However, in the case of the "good" worm, you're pretty much stuck with having to block certain traffic in a big ISP. The wonderful pings that it sends, coming from hundreds or even thousands of users on the same termination router, basicly turns into a massive ARP storm. This is enough to bring a device (which usually runs at 30-50% capacity) to the rev limiter, hindering the subscribers' ability to pass legitimate traffic, and creates a level of instability on the units (Hoorray for malloc errors in IOS!)

      An ISP shouldn't keep you from visiting tubgirl, goatse, or nambla, or doing whatever you want to do.. They should be prepared, and expected, to block a DOS attack, even if it is unwittingly coming from thier own users.

      --
      Squash
    17. Re:Ultimately... by mystik · · Score: 1

      Actually, that block seems to have been requested by the Dept. Of Homeland Security, according to my ISP.

      See:
      http://support.cox.net/custsup/safety/port_135.s ht ml

      --
      Why aren't you encrypting your e-mail?
    18. Re:Ultimately... by Anonymous Coward · · Score: 0

      And what about all these college? I've been hit many hundred times with e-mails from the SoBig virus yesterday. They all came from some college which apparently didn't bother to clean up their PCs. And I got many many e-mails from mailservers rejecting mails they received with my address in the From: address, also thanks to that virus and that college. Can't one sue these people for negligence? That's what I'd like toknow.

    19. Re:Ultimately... by Anonymous Coward · · Score: 0

      yes you do have a steering wheel on your computer.

      you obviousally dont understand...

      either OS' makers need to be FORCED to sell the software with all ports closed by default or force the user to pull their heads out of their arses.

      I think it's easier to force it upon the idiots that write and sell this obscure Windows product line.

    20. Re:Ultimately... by Sherloqq · · Score: 1

      Because I want to.
      Because I can.
      Because it's easier than trying to nail up some IPSEC tunnel between my Win box and someone else's.


      Until you educate the clueless masses out there (you could start with the ones sharing your ISP), guess what -- you're SOL. You're a minority. Most of your neighbors don't know that they're sharing their printer with the world -- and if they did, they probably wouldn't want to.


      It's connectivity, that's all.


      Precisely. And if my neighbor's cluelessness leads me to having NO connectivity because he's infested with two dozen viruses and trojans, YOU BET I'm gonna have them dealt with. Even if it means having ports firewalled off by my ISP. The benefits outweigh the drawbacks.

      Remember, it's all about security. Treat this the same way you'd treat your linux/windows box: you only run services you need, not everything the OS comes with. Why? Because to do otherwise is a waste. Because to do otherwise is irresponsible and careless. Like driving and yakking on a cellphone. Just because you can doesn't mean you should.

      --
      Have EVDO, will travel.
    21. Re:Ultimately... by mgkimsal2 · · Score: 1

      But they should already have some common sense.

      Sharing printers and whatnot over the internet isn't 'common'.

      For *most* people, using a computer isn't 'common'.

      Understanding TCP ports and virus attack methods isn't 'common'.

    22. Re:Ultimately... by GrenDel+Fuego · · Score: 1

      I see that as a good thing. What possible reason is there to have file and printer sharing open to the internet?

      Ok, but where do you stop? Hey, why only close the affected ports, when you can close all unused ports? Then you can save yourself the hassle of the next exploit.

      I'm guessing that was the thoughts behind one of the ISPs I deal with at work when they decided to lock down just about every TCP port (excluding 80 since these are webservers after all).

      Imagine our dismay when we tried to ssh into these linux boxes, and found that port 22 was now filtered. But I suppose if there is ever an ssh worm, those machines are now safe.

    23. Re:Ultimately... by azzy · · Score: 1

      > yes you do have a steering wheel on your computer.

      No I don't. I have a joystick, but it isn't connected, not used it for months.

    24. Re:Ultimately... by malfunct · · Score: 1
      I think the big downside to automatically enabled firewalls to the distributor is the HUGE increase in tech support calls of the nature: "I tried to install this program and it keeps telling me that the connection failed and to please contact my ISP." It may not outweigh the need for having security measures turned on, but its something that distributors don't want to deal with.

      There is also the fact that security is a prospect that is 80% education and 20% technology. The technology can ALWAYS fail but if a person knows what they are doing they can lower the risk and damage.

      What I could see as a solution is a 2nd internet type network for critical applications that requires special licence to join. Every transaction would be logged as to its originator and the orignator of a damaging transaction would be prosecuted.

      --

      "You can now flame me, I am full of love,"

    25. Re:Ultimately... by NDPTAL85 · · Score: 1

      A car is exponentially simpler to use than a computer is. There is no way you'd get public support for laws concerning personal negligence with respect to computers.

      --
      Mac OS X and Windows XP working side by side to fight back the night.
    26. Re:Ultimately... by Sleuth · · Score: 1

      Ha. They don't make cars, but Windows CE made it into BMW's cockpit controls on some models. There're a couple websites around with all kinds of humorous stories about when they go wrong...

    27. Re:Ultimately... by Anonymous Coward · · Score: 0

      it's NOT your port! It's their port on their router. If you don't like it, TOUGH!

    28. Re:Ultimately... by Shardis · · Score: 1

      Printer sharing isn't common? Why shouldn't we be able to do this if we really want to, and if it's done securely? Well, if you mean do %90 of users do print sharing, almost definately not. But I'd say it's common enough. A print server/service of some type is usually very common if you've got more than one computer networked together and want to print from both though.

      Anyway, sure, most of this is beside the point and uncommon for the average end user.

      What I'm mostly talking about is end users having some idea that just plugging their computer into the internet and then leaving it forever to be abused by whoever wanders by - is a bad thing!

      End users should have some basic responsability and accountability though. I'm sick to death of people just looking blank and shrugging and saying, "I'm not a computer person...", and using that as a license to quite intentionally never even try to take minimal precautions or learning / remembering / retaining even the smallest portion of what they're told. I run into this type of thing way too often, and it always astonishes me how apathetic people are.

      Granted, there are a few that care, but almost all of the non-techies that I know are actually comfortable giving this kind of reaction to even the most trivial technical operation. This is when I say stuff like "empty the recycle bin if you delete confidential info", or "don't mail 50MB attachments to a list of 500 people on the same server." (Yes, I know there are trivial ways around stuff like this, but I'm just using it to illustrate a point.)

    29. Re:Ultimately... by Shardis · · Score: 1

      Yeah, you're probably right. Usually once I fully explain why something like this might be a good thing, I usually have people agreeing with me though. Either that or people just don't say that they don't agree cause I get so irritated with stuff like this. heh. Too bad I'm not a politician though, and never really want to be one. I don't know why "internet laws" need to be any different than other laws, except usually in the case of jurisdiction. Breaking and Entering == A destructive unauthorized intrustion of a system, and etc...

      I tend to think that personal responsibility is almost a thing of the past these days, unfortunately. Especially in the corporate world. :(

  10. Imminent death of the net predicted by anotherone · · Score: 0
    Every time I hear about a huge new worm, I wonder how long until someone finds some huge exploit or something that will wreak major havoc over the entire 'net. What would the effects of that be, in the end? Seems like that would have a major effect on world economy.

    Of course, if they could re-do the internet, maybe they'd change some things, make it better... I smell an 'ask slashdot'.

    --
    Username taken, please choose another one.
    1. Re: Imminent death of the net predicted by Black+Parrot · · Score: 3, Funny


      > Every time I hear about a huge new worm, I wonder how long until someone finds some huge exploit or something that will wreak major havoc over the entire 'net. What would the effects of that be, in the end? Seems like that would have a major effect on world economy.

      Yeah, people would start getting their work done out of sheer boredom.

      --
      Sheesh, evil *and* a jerk. -- Jade
    2. Re: Imminent death of the net predicted by Flingles · · Score: 0

      I think it would be quite easily possible to do this for a good coder ie.
      Find a vulnerability for all OS's.
      Then it just keeps proliferating until a certain date, (say 6 months later) then just flashes the bios or performs fdisk.

      --
      Karma: -2^0.5 . Mainly due to the imbibing of dihydrogen monoxide
  11. Does this really even need pointing out? by Anonymous Coward · · Score: 0

    "Hardest hit was the 411 system..."

    1. Re:Does this really even need pointing out? by ewombatnet · · Score: 1

      "Hardest hit was the 411 system..." Gives a new meaning to the question "What's down with the 411" though, doesn't it?

  12. that's alright by toddhunter · · Score: 1

    Can't someone just right another worm to stop the worm stopping the worm?
    It's all getting a bit silly isn't it. The worse thing is that every incident like this is just another piece of ammunition for the pro-DRM companies.
    It also encourages the conspiracy theory people. After all why shouldn't Microsoft enjoy these worms so that people demand that their computers be locked down and be *safe* from the outside world

    1. Re:that's alright by nacturation · · Score: 1

      Can't someone just right another worm to stop the worm stopping the worm?

      Sure, but what happens when they left another worm?

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    2. Re:that's alright by Tim+C · · Score: 1

      The worse thing is that every incident like this is just another piece of ammunition for the pro-DRM companies.

      How does DRM prevent me from writing a worm? I think you mean trusted computing/palladium. Even then, though, I fail to see how it will prevent worm and virus writers.

      In order to be able to write my own software, there must be the provision to run untrusted code - they cannot shutdown an entire industry (shareware/freeware) simply to try to stop viruses. Therefore, the only practical effect I can see is that it'll be like installing an unsigned driver on 2k/XP. When you run the code, a dialogue box will pop up, warning you that it's not trusted and asking if you're sure that you want to proceed. Then it just becomes an exercise in social engineering, to get people to click "yes". They're already practising that, in order to get people to open the attachment in the first place; I don't see that being much of a barrier.

      Microsoft has a much, much better option for helping secure their users' computers though - they already ship with a basic firewall, and have recently bought an AV company. Turning the firewall on by default for any machine that is setup as a gateway (as selected in the "home and office networking" setup wizard), and shipping the AV software, on by default and auto-updating, would do a lot to prevent this sort of thing.

    3. Re:that's alright by Nucleon500 · · Score: 1
      In order to be able to write my own software, there must be the provision to run untrusted code - they cannot shutdown an entire industry (shareware/freeware) simply to try to stop viruses.

      You're right, they can't do that, but they can still try. And it's quite possible that shutting down non-proprietary software is the goal, and stopping viruses is the public justification.

    4. Re:that's alright by Keeper · · Score: 1

      Turning the firewall on by default for any machine that is setup as a gateway (as selected in the "home and office networking" setup wizard), and shipping the AV software, on by default and auto-updating, would do a lot to prevent this sort of thing.

      I believe they're considering turning on the firewall by default for home XP users. I also think they're considering having windows update configured to automatically apply critical updates on a default install. Though, this will be for the home version of XP only -- the logic being the corporate customers/people who know enough about computers to want some of the extras in Pro will know if/when they should do this on their systems. It will be interesting to see what they end up doing...though I'm sure there will be endless complaining here regardless of what they do though...:)

      I haven't heard anything on the AV front. I wouldn't expect any MS anti-virus software for quite awhile...

    5. Re:that's alright by jerw134 · · Score: 2, Informative

      I wouldn't expect any MS anti-virus software for quite awhile... Actually, a Microsoft anti-virus (among other things) program is currently in alpha stage. It's called the "PC Satisfaction Trial" and contains firewall, backup, and anti-virus tools. Although it's extremely buggy at the moment (which is to be expected with alpha software) it does look very promising. Even at alpha, it's simple enough for Joe User to figure out how to use it. I predict this program will be quite a big success.

    6. Re:that's alright by ctr2sprt · · Score: 0
      ObSimpsons:

      Skinner: Well, I was wrong. The lizards are a godsend.
      Lisa: But isn't that a bit short-sighted? What happens when we're overrun by lizards?
      Skinner: No problem. We simply release wave after wave of Chinese needle snakes. They'll wipe out the lizards.
      Lisa: But aren't the snakes even worse?
      Skinner: Yes, but we're prepared for that. We've lined up a fabulous type of gorilla that thrives on snake meat.
      Lisa: But then we're stuck with gorillas!
      Skinner: No, that's the beautiful part. When wintertime rolls around, the gorillas simply freeze to death.

      So clearly the solution is to discover the Internet worm equivalent of a gorilla that's susceptible to cold.

    7. Re:that's alright by superchkn · · Score: 1
      What the hell was their reason for not doing that in the first place?

      Let's see:
      remote buffer-overflow exploits known in Win95/98 +
      abundance of email worms !=
      default configuration is no security enabled

      I'm no rocket scientist, but I can quickly deduce that an empty administrator password and open ports to a connection created using a "Connect to the internet" dialog is a bad idea.

      How many of these machines are home users being infected I wonder? And how less effective would the worm be if even half the machines had these things implemented by default?

      Someone should write a worm that infects the vulnerable machine, then finds 2 other vulnerable machines and infects them, or times out. Right before deleting itself, prompt the user whether they are at home or business and log that to a website along with some other info about what IP this came from and how many machines it infected as well as their IPs. Maybe give the user the URL to a patch, but probably better just to leave a little note that we've been here so we can also track how many people just ignore the message and keep going...only to get infected again.

      That's legitimate research, isn't it?

      So, who's willing to fund my research?
    8. Re:that's alright by Moth7 · · Score: 1

      The writer of the "Anti-worm" did attempt to put in an equivalent of gorillas freezing to death, however we have to wait a little longer than until winter. The worm self destructs come 2004 which is in keeping with media reports as to how long blaster would be around. I admit, this is a long time, but there is no other way of doing it. You couldn't tell it to selfdestruct once it had found another victim because this would leave many people near the end of the worm's life permanently infected.

    9. Re:that's alright by Anonymous Coward · · Score: 0

      s/alpha/Microsoft/

      Oh come on, this is Slashdot.

    10. Re:that's alright by Anonymous Coward · · Score: 0

      In order to be able to write my own software, there must be the provision to run untrusted code

      Not necessarily. Look at Lotus Notes -- anyone with the tools can write code, and all code is automatically self-signed when it's saved. There's no such thing as anonymous code.

      It's not inconceivable that this could be done on the OS level. Just generate a One-Off cert, and trust it, and integrate the signing part with the tools.

  13. Article text by Magic+Thread · · Score: 5, Informative

    Since the article's filename is "flash1.html," I doubt it's staying in that location forever, so here is the text. Posting logged-in because of the insidious article text trolls that have been plaguing Slashdot recently.

    COMPUTER WORM THWARTS POWER SYSTEM REPAIR IN CANADA
    Tue Aug 19 2003 20:33:34 ET

    TORONTO (CP) - A computer worm designed to eliminate an earlier virus brought computer networks to a standstill Tuesday, hindering efforts in Ontario to recover from last week's power outage and forcing Air Canada to check passengers in manually across the country. Vancouver International Airport reported huge delays and long line ups in the international departures terminal as the virus slowed Air Canada's check-in computer system.

    Air Canada spokeswoman Laura Cooke said the virus affected the airline's call centre in Toronto and check-in systems across the country.

    ``It is causing delays in processing customers at airports,'' she said.

    The worm also slowed Ontario's efforts to repair the hydro system from last week's blackout.

    ``The system is under attack from the virus, and we've had more problems with this particular virus this afternoon than any other previous virus in Ontario,'' said Terry Young, a spokesman for the Ontario's Independent Electricity Market Operator.

    Inside the terminal in Vancouver, passengers, some of whom have been stranded since the blackout-related problems of last Thursday, were frustrated.

    ``It's a nightmare,'' said one unidentified woman. ``The service is so bad; the management was so bad. The system is just a mess, just a mess. I had my luggage delivered to Toronto, I was told on Saturday, so I don't have anything.''

    The worm targets computers running Windows 2000 and Windows XP and infected with the blaster worm. Once it deletes the blaster worm, the computer attempts to download a patch of the Microsoft update site, installs the patch and reboots the computer.

    It searches for active computers by sending a signal across the Internet, which results in significant increases in traffic.

    Internet security firm Symantec identified over 600,000 computers on Tuesday afternoon that were affected by one of the two worms.

    Telus, the country's second-biggest phone company, saw operations for 411 operators slowed as the worm infected a number of internal systems at the company, while Corus Entertainment's Web site was down until the company was able to clean up its system.

    The worm snarled the network at the CBC, slowing the broadcaster's Web site.

    The Blaster worm also affected some computers of Ontario's emergency response system dealing with the aftermath of last week's huge blackout across a swath of the province and eight U.S. states.

    Dr. James Young, the Ontario commissioner of public safety, said the problem was ``making our job more difficult.''

    Symantec assessed the worm a ``Level 4'' threat, the second-highest, due to reports of severe disruptions on internal networks.

    ``Despite its original intent, the W32.Welchia.Worm is an insidious worm that is preventing IT administrators from cleaning up after the W32.Blaster.Worm,'' Vincent Weafer, senior director of Symantec Security Response, said.

    ``The worm is swamping network systems with traffic and causing denial of service to critical servers with organizations.''

    It was not known where either of the worms originated. However, blaster, also known as lovsan because of a note it left on vulnerable computers _ ``I just want to say LOVE YOU SAN!'' _ also carried a hidden message to taunt Microsoft's chairman: ``billy gates why do you make this possible? Stop making money and fix your software!''

    Blaster exploited a flaw in most current versions of Microsoft's Windows operating system for personal computers, laptops and server computers. Although Microsoft posted a software patch to fix the flaw on July 16, many users failed to download the patch, leaving them vulnerable to the worm, which fir

    1. Re:Article text by s0l0m0n · · Score: 0

      `I just want to say LOVE YOU SAN!'

      Awww, it's so romantic...

    2. Re:Article text by Anonymous Coward · · Score: 0

      That is so much of an excuse it's not funny. Just like the Directory of IT for the Mayrland DMV saying that they had no advanced knowledge of the worm or patch and they handn't discussed it because it happened between their weekly meetings.

  14. Anti-worm patching worm? by FluxCapacitator · · Score: 1

    So...will there be another worm to patch the Anti-worm so it doesn't clog the networks? And if that screws up, will there be an Anti-worm to patch the original Anti-worm that ... oh never mind.

  15. Comment removed by account_deleted · · Score: 2, Funny

    Comment removed based on user account deletion

  16. How lame is their IT department? by nacturation · · Score: 4, Insightful
    From the article:
    ``The system is under attack from the virus, and we've had more problems with this particular virus this afternoon than any other previous virus in Ontario,'' said Terry Young, a spokesman for the Ontario's Independent Electricity Market Operator.
    So basically they haven't yet learned how to block port 135 on their networks? And they refer to a worm as a virus. I'm glad I don't live in Ontario right about now.
    --
    Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    1. Re: How lame is their IT department? by Black+Parrot · · Score: 5, Funny

      "The system is under attack from the virus, and we've had more problems with this particular virus this afternoon than any other previous virus in Ontario," said Terry Young, a spokesman for the Ontario's Independent Electricity Market Operator.
      > So basically they haven't yet learned how to block port 135 on their networks? And they refer to a worm as a virus. I'm glad I don't live in Ontario right about now.

      One suspects that the power companies in that corner of the world are oh-so-glad to have any random excuse right now.

      --
      Sheesh, evil *and* a jerk. -- Jade
    2. Re:How lame is their IT department? by WoTG · · Score: 4, Insightful

      Or maybe some people actually have a local network that uses port 135! As much as I like to knock the things that go on at Air Canada, I can't really blame this one on them.

      You can't usually block port 135 to all local traffic, because it has legitimate uses on MS networks. So, if a brand new worm or virus comes out, few if any anti-virus programs will detect it. Virus scanners, by-and-large are reactionary. They can't (usually) scan for what they don't know exist. It sounds like this particular worm was written to spread extremely quickly, and few had a chance to develop or update their virus definitions.

      Given this environment, all it takes is one machine to get infected before the entire network gets hit.

    3. Re:How lame is their IT department? by cbdavis · · Score: 2, Interesting

      That is what happened to us - someone brought
      their notebook from home ( with infection) and
      then plugged into IT network. Practice safe
      computing!!!

      In this kind of scenario, firewalls dont help.
      Cant block port 135 at routers 'cause we have apps at that port.

      Needless to say, our IT network is still reeling from this.

    4. Re: How lame is their IT department? by Black+Parrot · · Score: 1, Funny


      > Or maybe some people actually have a local network that uses port 135!

      Argh! My pacemaker!!!

      --
      Sheesh, evil *and* a jerk. -- Jade
    5. Re:How lame is their IT department? by Alien+Being · · Score: 1

      "Cant block port 135 at routers 'cause we have apps at that port."

      You could probably set up a filter like:

      src-or-dst-port==135 and "doesn't look like one of ours"

    6. Re:How lame is their IT department? by Anonymous Coward · · Score: 0

      "It sounds like this particular worm was written to spread extremely quickly, and few had a chance to develop or update their virus definitions."

      W32.Welchia.Worm exploits the same DCOM RPC vulnerability as Blaster. If they were infected with this is means they STILL HAD NOT PATCHED THEIR SYSTEMS and were STILL VULNERABLE TO BLASTER.

      After this has been in the news every day for over a week you think they would have spent the 5 minutes required to patch their systems.

    7. Re:How lame is their IT department? by Anonymous Coward · · Score: 0

      they also talk about people in vancouver's airport being stranded there since the blackout. . . Im pretty sure vancouver is in BC which is west canada and not affected by the blackout. But then again, I never really trust Drudge with much.

    8. Re:How lame is their IT department? by Anonymous Coward · · Score: 0

      From the article:

      ``The system is under attack from the virus, and we've had more problems with this particular virus this afternoon than any other previous virus in Ontario,'' said Terry Young, a spokesman for the Ontario's Independent Electricity Market Operator.

      So basically they haven't yet learned how to block port 135 on their networks? And they refer to a worm as a virus. I'm glad I don't live in Ontario right about now


      Don't forgot this is a spokesman making a statement to the mainstream press. Do you really expect the general public to understand or care about the distinction between "worm" and "virus"? More importantly, will they even understand what a "worm" is?

    9. Re:How lame is their IT department? by Anonymous Coward · · Score: 0

      Given this environment, all it takes is one machine to get infected before the entire network gets hit.

      why? it's too hard for them to apply the patch?

      your reasoning is redicilous.

    10. Re:How lame is their IT department? by Anonymous Coward · · Score: 0

      They're probably using Exchange as a Mail Server. See here (
      http://support.microsoft.com:80/support/kb/arti cle s/q150/5/43.asp&NoWebContent=1) for a list of ports used.

    11. Re:How lame is their IT department? by nacturation · · Score: 1

      they also talk about people in vancouver's airport being stranded there since the blackout. . . Im pretty sure vancouver is in BC which is west canada and not affected by the blackout. But then again, I never really trust Drudge with much.

      Air Canada services the entire country, so it's not surprising that if the main systems go down in Ontario the flights will be delayed in BC, assuming they all rely on those systems.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    12. Re:How lame is their IT department? by Anonymous Coward · · Score: 0

      your reasoning is redicilous.

      Your spelling is ridiculous.

    13. Re:How lame is their IT department? by Anonymous Coward · · Score: 0

      1) Why were people bringing in non-work laptops and plugging them into the network? Lart them with prejudice.

      2) If it was a work laptop, why wasn't it patched why didn't it have AV software installed and set to update its definition file whenever it can contact a server? Lart the person responsible.

      3) If lusers doing this is a problem, why not provide docking stations and physically wire them yourself. Put the docking stations on a seperate subnet, so if some luser still manages to break all the security measures, they cant disable your entire network with a flood of ICMP broadcasts. You can then gateway from their subnet to the main network with the ability to put effective traffic controls and firewalls in place; E.g. filter all ICMP traffic, do some sort of analysis on any NetBIOS traffic that they may need to send & recieve.

      If all else fails, just start shooting anyone who comes near you with a sheepish grin. They'll soon get the message.

    14. Re:How lame is their IT department? by Anonymous Coward · · Score: 0
      A little insider info here...

      It's *not* the MSBLAST worm they're dealing with, it's actually the new SoBig variant.

      Yes, if you thought they were stupid for getting nailed by MSBLAST, and that they must be really stupid for getting SoBig, you would be right.

    15. Re:How lame is their IT department? by Anonymous Coward · · Score: 0

      More to the point, in Canada just about every flight by Air Canada goes through Toronto's Pearson airport, even if that's not its destination (think of it as hub system, with only one hub). So when Toronto craps out most flights get cancelled because they have no place to go to.

    16. Re:How lame is their IT department? by Sherloqq · · Score: 1

      From what I've heard on the news last night, the power companies aren't having as much problem with the virus as Air Canada's computer systems do. And not just in Ontario, but across Canada (someone mentioned Vancouver for a change).


      I'm glad I don't live in Ontario right about now.


      Eh, it's not all that bad. If anything, I'd say I'm glad I'm not flying Air Canada right about now. As for electricity, we've dodged the supply/demand bullet yesterday, with Ontario supplying 20 GW of juice, and us using up 19.180 GW at 5pm. Today's weather forecast calls for higher temps and humidity levels. Worse come to worst, it'll be another opportunity to pop open a warm bottle of Labatt's/Canadian and chat with the neigh)$(@#&*(#*%&()*&#$@(*& +++ NO CARRIER

      --
      Have EVDO, will travel.
    17. Re:How lame is their IT department? by Anonymous Coward · · Score: 0

      All you need is a single fool connecting an infected laptop to the network...

  17. better idea by Anonymous Coward · · Score: 0

    Someone should write a "cleanup worm" that spreads for a while (a day or so) and then deletes everything on the infected computer's hard disk. This would solve the problem, because after a few days, there would no longer be many vulnerable machines left on the net :)

    1. Re:better idea by BiggerIsBetter · · Score: 1

      How about a worm that propogates around and closes ports behind it? Maybe something that enables the WinXP firewall as it goes. It doesn't have to be destructive to be useful.

      --
      Forget thrust, drag, lift and weight. Airplanes fly because of money.
  18. /. drudge? by ender1598 · · Score: 1

    What're the chances of the Drudge Report feeling any affect of this posting here? I mean, he's up there with google and yahoo for overall hits.

    --
    There are 10 kinds of people in the world; those that understand binary and those that do not.
  19. I applaud the idea. by danielsfca2 · · Score: 1, Insightful

    I think the dude who wrote it had a good idea... We had a discussion here about automatic updates... If people won't patch their own machines, then someone has to.

    However, the execution here was poorly thought-out. It should have been written to be far less agressive so as to avoid network slowdown. I would have had it scan for one hour per day, which hour would be chosen randomly. Then you cut traffic to 1/24 of the original level. Then have it de-activate and self-destruct after 5 pcs had been "infected" or 3 hours of scanning, whichever comes first.

    The thinking is, let a worm-writer take a crack at getting patches installed. If patches spread as quickly as viruses, this whole thing would never have happened!

    1. Re:I applaud the idea. by danielsfca2 · · Score: 1

      Excellent idea. I agree. Doesn't add to traffic at all.

    2. Re:I applaud the idea. by Build6 · · Score: 1

      It should just sit and listen for scan requests from MSBlaster

      Sounds like a good idea. Hrm. If I had mod points...

    3. Re:I applaud the idea. by quaxzarron · · Score: 1

      Oh right!
      Now we can have FDA approved 'patcher' worms released under virulent GPL going after M$ approved 'vulnerability detection' worms, chasing each other and crawling up and down the wires, looking for machines to declare battles and wars.

      Whoopeeeee, mama I wanna be a worm.
      ~!nrk

      --
      .sig(Anarchy Rules)
    4. Re:I applaud the idea. by Satan's+Librarian · · Score: 4, Insightful
      Uhm... no. Sorry. It's a bad idea. See this thread for additional comments from before this one hit.

      The original anti-virus virus was probably DenZuk, created to kill the Brain virus. They were both bootsector viruses. Problem is, later on a new format of floppy got introduced - DenZuk trashed users' data when it encountered them. And there wasn't a damned thing the original author could do about it, because it was self replicating, and therefore by definition not under his control.

      If you've gotta go vigilante, don't go viral. Do something you can control. Scan all the machines on the net and patch them, or just patch everything that bounces off your firewall - fine. It's likely to get you in legal hot water, and it is on questionable ethical grounds, but at least you aren't trashing random machines with self replicating code that you can no longer STOP, no matter how much you might want to.

      Any experienced programmer will know well that code that works on one machine is not going to always work on every other machine - no matter how good of a coder you are. Any smart and experienced programmer will also know that almost any complex program is going to run into a situation it wasn't designed for eventually and create an unexpected and probably very unpleasant result. Spend some time and think about it before acting.

    5. Re:I applaud the idea. by danielsfca2 · · Score: 3, Interesting

      I disagree. MrP's revision on my idea would:
      * Only infect machines already sick with w32.Blaster
      * Stop these machines from restarting due to the RPC process being terminated.
      * Stop these machines from causing network slowdown by scanning.
      Even if there was a problem with the code, it would still do more good than harm, because every machine patched would be one less flooding the 'net searching for machines to infect. It would not increase the traffic, because machines unpatched but uninfected would not be affected by this "good" worm.

      While I agree that in many situations, one might worry about releasing any worm into the wild, I think in this case the worst case scenario is it doesn't work. Which is the same as if you don't try at all, so there's little to lose.

      > Any smart and experienced programmer will also know that almost any complex program...

      Complex? This could be accomplished with a really small app. Its job would be incredibly simple:
      1. Kill blaster process, delete blaster app
      2. Attempt to download MS patch. If unsuccessful several times, terminate.
      3. Execute patch.
      4. Open relevant port 5. Wait for a connection.
      6. Transmit self to next machine.
      7. Has it been a week since last time scanned? If so, terminate.
      8. Goto 5.

      Sounds pretty simple to me, at least. I think it'd be pretty easy to debug.

    6. Re:I applaud the idea. by Satan's+Librarian · · Score: 2, Interesting
      I was right the first time, and quite honestly I think I'll be proven right again if it's done as you suggest.

      Not complex? You're downloading a bloody Microsoft Patch and running it! Have you seen how many people - competent administrators - have been saying all along that they have the automatic updates turned off because the patches keep breaking their machines? Ever written a buffer exploit? That's usually not simple code either, and it is very system and application specific - if the underlying code changes, but an overflow remains, your code will have completely unpredictable results. That's why the original patch for RPC prevented infection, but many patched computers that got probed still crashed.

      Also - this won't be done in a corporate environment with proper testing labs if it is done. You simply won't have legal access to the number and variety of machines you need to even get an idea that it might work properly right at the moment, much less "for all of its lifetime". The DenZuk example I provided is a perfect example of a pretty well written virus that went all wrong - the disks it corrupted didn't even exist when the author wrote it, and yet, it still caused damage.

      What happens when an uninfected machine attempts a legitimate RPC call? You infect it? Great.... You just broke someone's intranet that relied on RPC to get the job done, and you're preventing the legitimate program from binding to the port. Good job - pat yourself on the back, you just cost a company $1,000,000 in lost time during cleanup and lost customers.

      Someone's CMOS battery is dead and they reboot it once a day? Great! Worm never dies, hoses RPC forever for that machine.

      Bad idea. Mark my words on that.

    7. Re:I applaud the idea. by MillionthMonkey · · Score: 1

      Except that packets from w32.Blaster have spoofed source IP addresses, so this idea wouldn't work at all.

      I know you're just screwing around, but seriously, if I were in a development team with a programmer that sounded like you, I'd be mortified. You don't seem to have the proper respect for the code you're writing. A good programmer fears the code he writes. Almost every line of it might come back to screw you. Your program had better be 100% bug free if you release it using this distribution model, because there is no 1.0.1 release of a worm or a virus. If you find a bug or make improvements, the versioning problems are insoluble.

    8. Re:I applaud the idea. by s0l0m0n · · Score: 1

      Some virii are written with a specific location to look for updates, or leave open an additional obscure hole for patches to come through on a secondary distribution network.

      But you're completely right. There have also been virii that had redistribution systems which were *bugged*. Heh.

    9. Re:I applaud the idea. by Satan's+Librarian · · Score: 1
      Yep. And, many such viruses have their distribution site shut down within days (if not hours) of them hitting the wild - either from traffic overflow, or an administrator with just enough of a clue to think that maybe helping a virus along is a bad idea.

      The obscure hole of course defeats the entire purpose of the proposed so-called 'good' virus. It renders the machine even less secure.

      It's just a bad idea.

    10. Re:I applaud the idea. by danielsfca2 · · Score: 1

      Well, I'm not a programmer (I guess I should have said "IANAP"); I was simply suggesting a theoretical way to patch this vulnerability. If you're right that w32.Blaster spoofs source IP's, then I rescind the idea that a counter-worm is a good idea, since the only way, then, to do it would be way the current counter-worm is, and it's generating far too much traffic. Good observation.

  20. Not a good samaritan worm by Anonymous Coward · · Score: 5, Interesting
    If it were a good samaritan worm, why would it exploit the WebDAV hole, too? Fact is, this is a sneaky worm, not a prophylactic.

    It doesn't just kill the other worm. It replaces it. It's several orders of magnitude better at scanning, persists after reboot just like Blaster, and leaves a backdoor open, just like Blaster.

    OTOH, if you set your DNS to spoof "download.microsoft.com" and point it to an unproxied web server which gives it a different executable file instead of the patch it tries to pull, it will run that executable just dandy. Interesting things you can do to a worm-infected system besides patching it and leaving the infection intact are legion.

    1. Re:Not a good samaritan worm by Anonymous Coward · · Score: 0

      genius.
      now how are you going to change the infected computer's DNS?

      if you have that kind of access, you should be able to run just about anything, anyway.

      the only stupid design decision on this worm's part was not having it kill itself off after X iterations, or maybe prompt the infected machine after it had patched things.

    2. Re:Not a good samaritan worm by Anonymous Coward · · Score: 1, Insightful
      The download.microsoft.com spoofing assumes that you are in a position to control the DNS server(s) that respond to infected machines. Like if you're an ISP or a company with one or more internal DNS servers. If you're feeling real generous, you can parse the requested URL and transparently proxy all non-worm requests to the real download.microsoft.com.

      The genius of using a DNS hack to fix the worm is that checking download.microsoft.com is the first thing the worm does--nip it in the bud. Sure, you can patch machines by hand--but why not use the worm's own self-defense vector (patching behind its entry point) to kill it?

    3. Re:Not a good samaritan worm by eWarz · · Score: 1

      The hosts file in your windows\system32 folder can be edited quite easily

    4. Re:Not a good samaritan worm by Shardis · · Score: 1

      Actually I'd say that the only stupid design decision on this virus writer's part was designing and releasing the worm in the first place.

    5. Re:Not a good samaritan worm by netskip · · Score: 1
      OTOH, if you set your DNS to spoof "download.microsoft.com" and point it to an unproxied web server which gives it a different executable file instead of the patch it tries to pull, it will run that executable just dandy.

      How is that more ethical than writing a worm? You're still executing code on someone else's computer without their permission and not under their control.

    6. Re:Not a good samaritan worm by Anonymous Coward · · Score: 0

      By whom, from where?

  21. We've been hit by Anonymous Coward · · Score: 0

    I won't say who or where, but I will just say that this will definately pour fuel to the fire for forcing us to DMZ all of the doctors and the nursing students (we have been pushing for a while now). The virus we were infected with was the W32.Welchia.Worm. Brought over 600 clients down in less than 2 hours.

    "Look Ma! I can do it with no hands!"

  22. Re:My connection sucks by Black+Parrot · · Score: 3, Funny


    > My cable went out for about 2-3 hours earlier, and even before it went out everythings been slow, and still is.

    Yes, due to the state of emergency we'll all have to shoot for "second post" until this dies down, since the internet isn't physically fast enough to let anyone get a "first post" in right now.

    --
    Sheesh, evil *and* a jerk. -- Jade
  23. But, really! by agent+dero · · Score: 1

    It's not a bug, it's a feature.

    A feature MS wants you to patch and remove to optimize the feature's capability, really, I swear

    Don't you hate a linux geek that gloats >-)

    --
    Error 407 - No creative sig found
    1. Re:But, really! by standsolid · · Score: 1

      being the hardcore linux zelaot that i am -- i made this point at work to my co-workers (hardcore-hooray-for-windows techs).
      of course i pointed out that if microsoft just made it right in the first place... and the point if you compare the number of updates in linux and windows for stupid security holes like this one, it's almost unfair to put the OSes in the same category.

      the more amusing banter went a-something a-like a-this

      Me: It's so great to know I'm running a competing Operationg system for FREE that's immune to this attack. Itr amkes me all warm inside
      Co-Worker: And it's also really great knowing that if I buy a game/software off the shelf it's pretty much guaranteed to run on my Operating System
      Me: Sure, but too bad you only get to play it for one minute

      ah the sweet smell of gloating >:)

      --
      WTPOUAWYHTTOTWPA
      What's the point of using acronyms when you have to type out the whole phrase anyways?
  24. Comment removed by account_deleted · · Score: 5, Insightful

    Comment removed based on user account deletion

  25. Oh FFS! by marcushnk · · Score: 3, Funny

    If they just made sure their bloody networks were patched and firewalled correctly they wouldn't have this issue..

    Frankly I think that anyone that complains about this needs a good hard leson in cause and effect.. oh hang on.. looks like they're getting that now!
    Lets hope they're bright enough to recognize it.

    --
    "Consider how lucky you are that life has been good to you so far. Alternatively, if life hasn't been good to you so far
    1. Re:Oh FFS! by cbdavis · · Score: 5, Insightful

      We got this crap at work. Firewalls didnt help
      because someone in the office took his notebook
      home, got infected and then brought notebook
      into work. Silent infection. You can build
      multiple firewalls but it is worth nothing if
      your users dont protect their networks at home.

    2. Re:Oh FFS! by marcushnk · · Score: 1

      I don't want to seem like I'm having a go at you.. but a firewall is only stage 1 of protection.. We consider laptops to be our second level of security risk.. purely because of their portability.. so our site had the laptops covered in the same day we had to make sure all the servers were covered.. Desktops were the last on our list..

      --
      "Consider how lucky you are that life has been good to you so far. Alternatively, if life hasn't been good to you so far
    3. Re:Oh FFS! by rsax · · Score: 0
      Lets hope they're bright enough to recognize it.

      The comment is marked funny but it's the last little bit that really made me smirk. There are dumb (or lazy) people everywhere using computers on the internet which probably is why I still receive connection attempts from computers infected by Nimda. I stopped hoping a looong time ago ;)

    4. Re:Oh FFS! by R.Caley · · Score: 2, Insightful
      Firewalls didnt help because someone in the office took his notebook home, got infected and then brought notebook into work.

      If you let people plug random machines into your network, you, to all intents and purposes, don't have a firewall.

      Laptops which visit the outside world need to be treated as external machines, not internal ones.

      --
      _O_
      .|<
      The named which can be named is not the true named
    5. Re:Oh FFS! by marcushnk · · Score: 0

      Oh you Cynic you...

      --
      "Consider how lucky you are that life has been good to you so far. Alternatively, if life hasn't been good to you so far
    6. Re: Oh FFS! by Black+Parrot · · Score: 1


      > We got this crap at work. Firewalls didnt help
      because someone in the office took his notebook
      home, got infected and then brought notebook
      into work. Silent infection. You can build
      multiple firewalls but it is worth nothing if
      your users dont protect their networks at home.


      Never heard a better argument for safe sex.

      --
      Sheesh, evil *and* a jerk. -- Jade
    7. Re:Oh FFS! by Spoing · · Score: 1
      Firewalls are useless if you still have running services on open ports!

      If the service isn't running, there's nothing to protect.

      If the firewall is up, but a service has a hole in the firewall, it is like no firewall is in use at all for that port. At that point, you have to trust what is exposed.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    8. Re:Oh FFS! by Lumpy · · Score: 1

      Firewalls didnt help
      because someone in the office took his notebook
      home, got infected and then brought notebook
      into work.


      decent security policy on your pc's coupled with deactivating the ethernet and other ports on a machine solve this problem.

      Hell I even take their floppy drives and CD drives replacing them with an extra battery.

      It's MY computer, not the users. and damned if I am going to let them compromize everyone else so they can install AOL on it.

      I have never had a virus come from one of my pc's in fact the last round came from the CTO who connected from his vacation home via vpn, who demands he runs as administrator.

      remember kids, just because you are the CTO of a large company doesnt mean you actually have any brains.

      --
      Do not look at laser with remaining good eye.
    9. Re:Oh FFS! by Odin's+Raven · · Score: 1
      We got this crap at work. Firewalls didnt help because someone in the office took his notebook home, got infected and then brought notebook into work. Silent infection.

      However, if your IT department had actually updated the machines with the fix that MS released last month, then the rogue laptop wouldn't have been able to infect the other computers. Firewalls are only one part of a security strategy -- maintaining/updating the system software is also rather important, as your post aptly illustrates. (And keeping things updated is just as important whether you're running Windows, Linux, or any other OS.)

      You can build multiple firewalls but it is worth nothing if your users dont protect their networks at home.

      And yet you'd still be vulenerable if a lazy sys admin hasn't patched your work machines against the two hundred assorted security holes that were fixed after your OS was originally released. Even if you banned commuter laptops at your office, it'd only take one clueless desktop luser who still hasn't learned their lesson about opening email attachments to infect your network. (Remember that a variation of this worm was being propogated via an email attachment, and MSBlaster is hardly the only virus/worm that gets sent around this way.)

      Yes, your rogue laptop user needs a liberal application of the old cluestick. But it sounds like your IT boffins need a few wake-up bonks as well.

      --
      A marriage is always made up of two people who are prepared to swear that only the other one snores.
    10. Re:Oh FFS! by PimpNinjaWannaBee · · Score: 0
      We got this crap at work. Firewalls didnt help
      duh! haikus are only allowed to have five syllables on the first line.
    11. Re:Oh FFS! by DukeyToo · · Score: 1

      Ah! You! BOFH!

      I pity your users...what's next, their keyboards? Their screens maybe?

      --
      Most writers regard truth as their most valuable possession, and therefore are most economical in its use - Mark Twain
    12. Re:Oh FFS! by Sherloqq · · Score: 1


      If you let people plug random machines into your network, you, to all intents and purposes, don't have a firewall.
      Laptops which visit the outside world need to be treated as external machines, not internal ones.


      Amen to that. Additionally, all laptops (or other devices one takes home / connects to other 'foreign' networks) should be segmented into their own separate subnet at work and firewalled accordingly. For the people that take their hard drives home instead, their work machines should have a virus check thoroughly scan the drive every time they bring it back.

      I know, these are lofty ideas, but at some point dealing with reactive stuff gets annoying and tedious enough that there is no other way.

      --
      Have EVDO, will travel.
    13. Re:Oh FFS! by Lumpy · · Score: 1

      yes. Yes I am.

      The Ethernet in the Dock works. so when docked they have full access to the network services and I automatcially back them up to the server so they never lose documents, Hell they can fax from their desktop and print to a pdf printer I set up for them.. they have many services and tools HERE under my control.

      Hell I'll even configure it for their printer at home. but they are NOT connecting it to a damned thing outside my control.

      I even run trust no EXE on all their machines. go ahead and download hotbar or webshots... it is not going to install!

      solves the problem very well.

      --
      Do not look at laser with remaining good eye.
  26. DRM by veldmon · · Score: 1, Interesting
    This is a perfect example of why we need DRM, and specifically MS's palladium implementation of it for Windows (where the biggest problem is). There's really only a very small chance that it could be detrimental to the Free Software movement.

    For example, if I were to to write a virus that called one of the myriad of registry functions in Windows, my virus would have to be registered for authentication with MS beforehand. It is highly unlikely that MS's inspectors would not notice the harmful intent of my code.

    Although there is a lot of fear about DRM in the Free & Open source communities, there need not be in reality. This is for two reasons. First, it would not be difficult to craft an open source DRM specification and submit it to the W3C. This means it will not be patentable. And second, with the registration mechanism handled through the W3C, developers would only have to submit their code for DRM authentication for a small fee of 1000-2000 dollars. This could easily cover the W3C's administrative costs, and would be economically viable for open source developers.

    Just my $00.02.

    1. Re:DRM by shibashaba · · Score: 2, Insightful

      Yes and what about when web sites and media start requiring DRM/Palladium whatever crap computers and operating systems to access their sites? What about when an ISP requires it to connect to their service? Web developers seem to be pretty braindead about the way they put a lot of sites together as it is(and no I don't care how many people I offend). Comcasts homepage uses actually has a flash dialog come up telling me that I need to install flash to use one of the features! This will shut out opensource companies effectively. Do not try and pretend this will be handled threw the W3C or anyone else who is impartial. Microsoft is the biggest pusher of security through obscurity and will not allow anyone to make an opensource implementation or put it up to a standards community like them. It goes against everything they've been saying. And what good are certificates anyway? Half the web sites can't even figure out how to renew their certificates in the first place, not even the trustedcomputing site. With the system you describe anytime some software company you bought from doesn't renew their subscription you won't be able to use your software that you spend hundreds of dollars on. And if there permanent there's nothing stopping people from somehow using the same certificates in worms or viruses. People can modify programs installing rootkits that have the same crc as the original software. Furthermore, what happens when the security for any part is broken? Now the malicious code/hacker is completely trusted. I'm making a lot of assumptions here on the exact implementation, and nothing I've said is original, but whatever it comes down to is the system is crap. It hasn't kept the xbox and playstations, dvd players, or windows media from being cracked -- and these are small fish compared to how extensive microsoft wants to see this stuff implemented. It is targeted at people like you though, that just want something to make you feel good and give people excuses for not thinking about security or monitoring their systems.

      --
      ---------- Open Source is capitalism applied to IP.
    2. Re:DRM by freeweed · · Score: 1

      Is this a troll or what?

      Maybe I'm missing something, but the day I have to pay $1000 just to write some Windows software is the day I (and many, many others) stop writing free software.

      I know, I have a better solution. STOP SHIPPING OPERATING SYSTEMS WITH A DOZEN OPEN PORTS, BOUND TO SERVICES 99.999% OF YOUR USERS DON'T USE.

      --
      Endless arguments over trivial contradictions in books written by ignorant savages to explain thunder in the dark.
    3. Re:DRM by Nucleon500 · · Score: 1
      There's really only a very small chance that [Microsoft's implementation] could be detrimental to the Free Software movement.

      Microsoft wants to harm free software; and they certainly won't mind if they accidently hurt it with their Palladium implentation.

      For one, while it might stop viruses and trojans (until the users are conditioned to clicking "Run unsigned code"), it won't do anything against worms and overflow expliots. Second, as you say, it would be required that source code be submitted to "MS's inspectors" and compiled by them. And as you say, they won't sign "viral" code. Consider what kind of code Microsoft considers viral. And finally, a $1000 - $2000 fee certainly isn't economically viable for open source developers.

    4. Re:DRM by CoolMoDee · · Score: 1

      Man, imagine how much it would cost just to get a CS degree..1000 - 2000 dollars to run each program on your desktop that you wrote. Im sorry, but I don't even have enough money for a single DRM "authentication let alone enough for each program that I write...and 1000 - 2000 dollars is not economically viable for open source developers when most projects have zero money to work with.

      --
      Jisho - A Japanese English German Russian French Dictionary for the rest of us.
    5. Re:DRM by Nucleon500 · · Score: 1
      Maybe I'm missing something, but the day I have to pay $1000 just to write some Windows software is the day I (and many, many others) stop writing free software.

      Most people wouldn't stop writing free software, they'd just stop writing it for Windows. Ironically, Microsoft seems bent on increasing it's TCO, and forcing open source to concentrate on it's own OSes.

      When I first used Linux, I was trying to be a Windows coder, but I didn't want to pay $300 for an optimizing C++ compiler, after having just found GCC, the GNU tools, Linux, etc. It's not smart for Microsoft to raise the barrier of entry for Windows developers; they're already hemorrhaging mindshare.

    6. Re:DRM by jake666 · · Score: 1

      I'm willing to bet that at least 50% of the "freelance" windows developers out there wouldn't pay anyways. After all, we're supposed to pay for Photoshop as well, and we don't see that happening.... Opensource is going to thrive on Windows whether it pays for it or not.

      --
      -jake
    7. Re:DRM by Satan's+Librarian · · Score: 4, Insightful
      Trolling, or just innocent? DRM could help slow the proliferation of viruses somewhat, but - I doubt it will actually fix worms like this. What it can do is prevent unknown hostile programs from running in the first place - if you're running an executeable directly. I think it is a good idea, but more from a corporate administrative standpoint - no more stupid users installing KaZaa.

      But can DRM truly be the solution to prevent exploits and worms? I doubt it. I expect that it will be trivial to exploit a program that's already been verified and make it do something it shouldn't even with fairly well implemented DRM.

      Email viruses may be halted in their tracks - but most exploits will most likely not be. You say the Palladium implementation of DRM is sophisticated enough to detect a code change during runtime from a stack overwrite? I doubt it, but if so - just change the data instead. Same effect. It raises the bar, but viruses share a characteristic there with open source - the bar only has to be hurdled once before the flood. See the recent rash of RPC hole worms and exploits - one guy did it, now everyone and their 12 year old can.

      And licensing a piece of software for $1000-$2000 so that it could run in the first place is ridiculous. Do you like freeware, shareware, or open source? It'd kill it on that platform. Might be great for the competing platforms, but not the one it's on.

      I think the real threat with DRM though is that it'll be used in the ways we've already seen, only more expansive. Wanna play a DVD you bought on an unauthorized operating system? Pay the fee, or, if the owners are too lazy to write software for your OS, just forget about it. And don't even think about writing a program to play it for you if you value your freedom.

      If left unchecked, CD's will become that way. Downloadable audio has already started to. Tried to download an mp3 from iTunes on Linux? Find anywhere else you can get the same tunes legally? For now - yes, just buy the CD. For now. Hopefully consumers will be upset enough as use of such copy protection schemes increase to purchase alternatives. I subscribe to E-Music myself - no DRM, but I'm paying for the industry to create more, and mostly to smaller lables (mainly Napalm, if they keep track - bands like Tristania, The Sins of Thy Beloved, etc).

  27. And this is bad? by rossz · · Score: 4, Interesting

    So the networks are brought to a crawl due to the large amount of traffic necessary to patch systems because incompetent MSCEs are too incompetent to do the job themselves?

    Well cry me a fucking river.

    With all the worm and virus activity in the last few months they have absolutely no damn excuse for not being on top of this. Since they are too stupid to do their job, someone found it necessary to do it for them. Personally, I would have considered a disk formatting worm to be fully justified.

    --
    -- Will program for bandwidth
    1. Re:And this is bad? by Kris_J · · Score: 1
      Personally, I would have considered a disk formatting worm to be fully justified.
      I'm starting to believe the same thing myself. Thing is, once the PC is rebuilt what are the chances that it will be patched properly?

      Someone should scan the whole damn planet using HFNetChk with the credentials of Username: Administrator, Password: [NULL] and automatically push any missing patches.

    2. Re:And this is bad? by gregarican · · Score: 1
      True that. Around my area I see on the news where three major hospitals were without computer resources due to getting hit. Interesting. It's like this:

      Fail to apply the patches to fix a vulnerability that was discovered in 11/2002 and announced 7/2003. Microsoft sent e-mails to everyone on their security bulletin mailing list informing them of the severity. Even the Department of Homeland Security piped up.

      Then have the entirety of the network --- from prescription workgroups to patient record workgroups to ER workgroups --- as one open playing field. Physical or logical subnetting is out of the question.

      What makes this all the more ludicrous is that these places were relying on Windoze for mission critical functions and one place just was hit yesterday! No rush on patching things up I suppose.

      Who says that hospital and banks should abandon their *ancient* mainframes and enter the 21st century? At least mainframe experts aren't some paper MCSE who are like deer in headlights when it comes to frontline troubleshooting and maintenance!

    3. Re:And this is bad? by Anonymous Coward · · Score: 2, Informative

      yeah, yeah, blame the user, blame the user.

      Have you totally ignored the discussions about this worm? The fact is that many people took Microsoft's advice, applied the patches and still got compromised. This is a massive failure on Microsoft's part:
      1. for releasing yet another buffer overrun hole in their systems. The coding problems that cause this are well-known, the tools to search for it can be automated, and MS claims to have an army of people searching for these vulnerabilties by hand. Yet one of the affected systems is Windows Server 2003!
      2. They fucked up the fix! The first round of fixes for this vulnerability turned off the DCOM services to the outside world, but left the server listening at the same port and vulnerable to a buffer overflow! Stupid! Stupid! Stupid!
      3. Many claim (and I haven't verified this myself) that the updates said that the fix was already installed when it wasn't. Seems like the registry changes that MS uses to verify that patches were installed are made before the actual patch is installed. If the patch process punted while installing the patch, but after the registry changes were made, it would never try to install it again. Stupid! Stupid! Stupid!

    4. Re:And this is bad? by theFool · · Score: 1

      What makes this all the more ludicrous is that these places were relying on Windoze for mission critical functions

      I work in a hospital's IT department. Have you seen the healthcare-centric software and applications out there? We have 80 or so Win2000 servers to run our systems. Most of the systems we use are windows only, other applications just won't function. Just try to find _any_ software thats designed for some of our special needs, let alone Free software.

      Additionally, we have been 100% free of all the major viruses of the past six months. Why? Diligent virus scanning patching, and firewalling.

      The viruses we get are all because of stupid users opening attachments (though we once got a virus from a vendor's system that we lease and couldn't scan)

      What's my point? Well, if you are diligent (daily updates to all virus scanners, and no machine without one... McAffe has a very nice system called EPO) you won't get a virus.

      --
      LINK : LNK6004: Sig not found or not built by the last incremental link; performing full link
    5. Re:And this is bad? by rossz · · Score: 1
      Just try to find _any_ software thats designed for some of our special needs, let alone Free software.
      When you have highly specialized needs, all too often the software must be a custom job. Insist on non-Windows software. There is absolutely no good reason to run mission critical software on an unstable platform. People might die.
      though we once got a virus from a vendor's system that we lease and couldn't scan
      I hope the legal department was all over that vendor like stink on shit with the magic words "liability". I hope the IT department insisted the vendor make it possible to run regular virus scans on it.
      --
      -- Will program for bandwidth
  28. Re:My connection sucks by danielsfca2 · · Score: 1

    My cable (internet) went out for a couple hours earlier, too. I called Adelphia and the guy told me "Looks like you're part of an outage. From Ukiah (California, my town) to Los Angeles."

    Of course, Adelphia doesn't serve a large amount of markets in that area, but anyway, I wonder if it's really because of this. Somehow I'll bet it's not. It wasn't like it was slow, it just couldn't even sync upstream.

    What is your ISP and metro area?

  29. Any advice to a budding worm writter? by iamacat · · Score: 1

    On how to shape the "patching worm" activities so that it continues scanning for infected machines without causing serious congestion. Would it be enough for one of the worms to quit if it finds another one on the same subnet? Or should the worm just run for fixed time on each vunerable node it finds and patches and then quit permanently?

    Actually this is a hypothetical question. I don't think Windows users can be helped by installing just one patch. More radical solutions are needed, like pointing them to the nearest Apple store. Someone with way more free time than me can consider writting a worm that activates XP firewall on every network interface and disables ActiveX in IE and OE.

    But writting a truly benefitial warm/virus is still a fasinating topic to think about. Any thoughts?

    1. Re:Any advice to a budding worm writter? by Flingles · · Score: 0

      For no reason I love the idea of creating a nice worm. I thought that in THIS situation it would scan for say three minutes, and if it found an open port, upload itself to that computer. If after 3 minutes none were found it deletes itself. If it finds one it deletes itself. That way eventually if every computer doesn't have this vulnerability it will become extinct. Whereas the current one keeps going on and on.

      Also it would tell the user what it's doing at the time. Darn fine idea I say.

      --
      Karma: -2^0.5 . Mainly due to the imbibing of dihydrogen monoxide
    2. Re:Any advice to a budding worm writter? by Satan's+Librarian · · Score: 1
      Sure, I've got some advice. Don't.

      I posted some of the reasons before this one appeared here and here, and followed up in the comments to this article here.

      Basically, the problem is - no matter how good your intentions are, you're going to hose some machines and cause real problems. You won't have control over the code once it is released. Even if you just publish source for it, someone else will release it and you won't have control.

      If you want to help people, write your firewall activation and configuration program as a tool that allows the user to control it and distribute it freely on a website. Advertise it. If it doesn't suck, people will use it and you'll help make the internet more secure. Popular magazines might even recommend it as a really easy fix for security, and you'll help even more people. And, if you screw up, you can fix the bugs in the next version and provide support. Added bonus - the police and corporate lawyers won't be hunting you.

      If you just want to flex your coding muscles, try writing cool stuff that you can put on a resume without being arrested. Or go help out on something useful that people will thank you for. If you really want to pit your code against others, try CoreWars - kinda old school, but it doesn't screw up anyone else's day.

      At the very least, please read this paper.

      If you've got enough skill to write a worm from scratch, you've got enough skill to either a.) make real money with programming, and/or b.) write useful software that will help lots of people. Don't waste your talent.

  30. yea baby by codepunk · · Score: 1

    Tell me about that TCO now!

    --


    Got Code?
  31. my thoughts by loraksus · · Score: 2, Interesting

    For what it is worth, MS and others should do something like this _EVERY_ time a full root vunerability is exploited by a released worm, virus etc. So it may stop an app from working, etc. At least a virus didn't fdisk your hdd. Minor patches be dammned, vunerabilities that give the attacker root or equivalent access NEED to be taken care of ASAP.

    If the dumbass sysadmin didn't decide to patch his system, the writer of the software (note I don't think this should be limited to MS) should take it upon themselves to fix it.

    If not immediately ater, then a couple days.
    Now. I understand that ms hotfixes tend (AHAHAHAHAHHAHAAH, tend) to screw stuff up. A simple flag in the registry / file in the filesystem could tell the "viral exploit patch", not to patch the system, but send the administrator a message / put a link on the desktop for the patch. Of course, the next worm could just set that flag after infection, so this idea kinda sucks, and which is why I'd reccomend the radical option of no way of overriding the "viral exploit patch".

    Yeah, flame me and mod me down, but it is just plain fucking stupid and irresponsible to leave a system in a vunerable state. When exploits begin to affect infrastructure (whether it be 411 or whatever), they NEED to be taken care of. There are plenty of IT morons who leave critical systems (ok, define critical) open, and it is just a matter of time before something happens and many people actually get hurt.

    And to be completely honest - if the "viral exploit patch" hits your internal network, the destructive one could of have just as easily gotten in, that isn't an arguement.

    Reporting back to a central server would be cool, although how it would differenciate between many internal networks, the code would need to be optimized to minimize disruption, etc.

    Personally, I think whoever wrote blaster was doing the community a favor, some skript kiddie would eventually write their own version that did something far worse.
    Sure, I'm kind of bitter, but crap like this pisses me off - if gives the IT industry and computers in general a bad image. If it turns out that some hick in ohio forgot to patch his servers - servers that were rebooting when they were supposed to be sending out warnings to other power stations . . .

    Soooo. . . who think's I'm going to have an ulcer in 10 years ;)

    --
    1q2w3e4r5t6y7u8i9o0pqawsedrftgthyjukilo;p'azsxdcfv gbhnjmk,l.;/
    1. Re:my thoughts by DarkZero · · Score: 1

      For what it is worth, MS and others should do something like this _EVERY_ time a full root vunerability is exploited by a released worm, virus etc. So it may stop an app from working, etc. At least a virus didn't fdisk your hdd. Minor patches be dammned, vunerabilities that give the attacker root or equivalent access NEED to be taken care of ASAP.

      ---

      Now. I understand that ms hotfixes tend (AHAHAHAHAHHAHAAH, tend) to screw stuff up. A simple flag in the registry / file in the filesystem could tell the "viral exploit patch", not to patch the system, but send the administrator a message / put a link on the desktop for the patch. Of course, the next worm could just set that flag after infection, so this idea kinda sucks, and which is why I'd reccomend the radical option of no way of overriding the "viral exploit patch".


      The problem with this idea, even in the form of just putting a little message or icon on an infected user's desktop, is that it creates a single point of entry. Microsoft's internal servers have been hacked, and, in fact, utterly 0wn3d, in the past. If that happened again and some new version of Windows allowed them to send information to users' computers and have it automatically downloaded, then someone could annihilate every Windows machine connected to the internet in the entire world with one stroke.

      It's like those towns in RPGs and fantasy novels that all get their water from the same river. The bad guys just have to go upstream and poison the river and they can wipe out an entire string of towns. It's the classic problem of a large number of people relying on a single vital resource that can be tainted by enemies.

    2. Re:my thoughts by jwang · · Score: 2, Funny

      ...someone could annihilate every Windows machine connected to the internet in the entire world with one stroke.

      Now that you mention it, that doesn't sound so bad...

    3. Re:my thoughts by loraksus · · Score: 1

      Thats why the ability to override the patch should not be available.
      I'm not reccomending an update thru windows update or some "official ms" server either. The patch needs to be distributed via the security hole itself - in a viral manner. The thing is, if there is an exploit that gets full root, it really doesn't matter what the consequences of applying the patch are - it is better than getting your data wiped or even worse corrupted / stolen.

      --
      1q2w3e4r5t6y7u8i9o0pqawsedrftgthyjukilo;p'azsxdcfv gbhnjmk,l.;/
    4. Re:my thoughts by Anonymous Coward · · Score: 0
      Microsoft's internal servers have been hacked, and, in fact, utterly 0wn3d, in the past.

      How about some "facts" with your supposition?

    5. Re:my thoughts by DarkZero · · Score: 1

      Facts. I pulled up the story from The Register because the Wall Street Journal is probably a lot harder to wade through, but this should jog your memory. Microsoft was hacked and the hackers supposedly had access to the system for three months before they were detected.

  32. Why weren't these systems patched? by chill · · Score: 5, Interesting

    Considering the original and first variant of the MSBlaster worm made major headlines, why were these systems still vulnerable?

    Are each of those systems equipped with a 9-volt battery and a cheap Somebody Else's Problem field?

    And don't give me that shit about airline computers having to be 24x7. If that were the case, they wouldn't be running Windows in the first place.

    --
    Learning HOW to think is more important than learning WHAT to think.
    1. Re:Why weren't these systems patched? by Jugalator · · Score: 1

      And don't give me that shit about airline computers having to be 24x7. If that were the case, they wouldn't be running Windows in the first place.

      No, and the only way for them to make them possibly run 24/7 is to patch that security hole. :-) Until then they don't even stand a theoretical chance. So, yes, it's a mystery. I guess they just don't know enough about computers or care. lol

      --
      Beware: In C++, your friends can see your privates!
    2. Re:Why weren't these systems patched? by Anonymous+Freak · · Score: 1

      Well, I run a computer consulting company (which was VERY busy last week, slowed down considerably this week, but still above average,) and I had a customer today who was on vacation with no internet access until today. He got home, connected to the internet to download the patch, and caught this new one within 1 minute of logging on. (Ironic, because he thought it was blaster, and called my company to have us come and patch his system. I saw what had happened, told him not to worry about it, got rid of this worm and disabled tftp.)

      --
      Another non-functioning site was "uncertainty.microsoft.com."
      The purpose of that site was not known.
    3. Re:Why weren't these systems patched? by duffbeer703 · · Score: 2, Informative

      STFU

      Try patchin 75,000 workstations and servers in a month with 100 IT staffers who have jobs to do besides patching MS shit.

      --
      Conformity is the jailer of freedom and enemy of growth. -JFK
    4. Re:Why weren't these systems patched? by Anonymous Coward · · Score: 0

      Simply because many people have a pirated or the infamous bootleg Windows XP version and windowsupdate might recognized 'pirated' WinXP version and refuse to update.

    5. Re:Why weren't these systems patched? by Anonymous Coward · · Score: 0

      Considering the original and first variant of the MSBlaster worm made major headlines, why were these systems still vulnerable?

      Are each of those systems equipped with a 9-volt battery and a cheap Somebody Else's Problem field?

      And don't give me that shit about airline computers having to be 24x7. If that were the case, they wouldn't be running Windows in the first place.


      They don't care - it's AIR CANADA. Their motto for a long time has been, "We're not happy until you're not happy!"

      And they're in bankruptcy protection.

      And they've paid large bonuses to keep "critical senior management" through the bankruptcy protection. If they were that critical, they wouldn't have drove the company into the ground.

      It's quite sad, it used to be a decent airline. But the sooner it dies, the better.

    6. Re:Why weren't these systems patched? by Anonymous Coward · · Score: 0

      Except patching them means a reboot which means...no 24/7! So the original poster is right; if those systems really had to be 24/7, they wouldn't be running Windows. Actual 24/7 is damned difficult to achieve even with a Dinasour thats been designed to do it, let alone an Intel box running Windows.

    7. Re:Why weren't these systems patched? by Anonymous Coward · · Score: 0
      STFU Try patchin 75,000 workstations and servers in a month with 100 IT staffers who have jobs to do besides patching MS shit.

      Such language, do you treat your users like that?

      I'll give you a tip mr. STFU man, in Windows they have "automatic update" that you can turn on, and the *users* will do this job FOR YOU. Isn't that amazing? Microsoft will even let you setup a local mirror of Windowsupdate so you don't need to kill your outbound internet connections with it! If you have 75,000 workstations you *must* have a spare one you can run this on.

    8. Re:Why weren't these systems patched? by Anonymous Coward · · Score: 0

      There's automated solutions out there, helpdesk monkey.

    9. Re:Why weren't these systems patched? by Anonymous Coward · · Score: 0

      Fuck you. At least you still have 100 IT workers.

      Also - if you are too stupid to automate a distribution of a patch file - (ever hear of SMS? Norton Console? PSEXEC?) - or if your boss is too stupid to trust remote computing - all of you should be taken in the street and shot.

      If all of your 75k computers all are built to internal standards that duplicate the operating environment from machine to machine, than this should be real easy.

    10. Re:Why weren't these systems patched? by Qrlx · · Score: 1

      Ahem, perhaps someone should have thougnt of this sort of thing *before* deploying 75,000 workstations?

      It's not like viruses are new. Michelangelo was like what, 20 years ago? (Actually I just looked it up and it was 1992. Which is around 500 BC in computer years.)

      It sounds to me like you're understaffed and overworked. Nobody gives a flying fuck so long as your stock is doin' well. God Bless America!

    11. Re:Why weren't these systems patched? by Blackknight · · Score: 2, Insightful

      Maybe you should learn how to deploy patches and updates the right way then. Set up an SMS Server, and deploy the patches to every workstation in the domain overnight.

      We did it with a few thousand workstations at my old company and didn't have that much difficulty with it.

    12. Re:Why weren't these systems patched? by duffbeer703 · · Score: 1

      Haha!

      Try doing that in a nightmare legacy NT4 domain clusterfuck. 300 domains in thousands of sites with everything from NT 3.51 to XP and bandwidth from 56k to OC-192.

      --
      Conformity is the jailer of freedom and enemy of growth. -JFK
  33. Innoculants, the medical profession by comparison by TWX · · Score: 1

    The Hyppocratic Oath, the "do no harm" oath, apparently hasn't been translated into computing yet.

    Regardless, if this worm's malevolence level is as benign as it sounds, more development in this area might need to be considered. Better delivery of course, but the concept is interesting.

    --
    Do not look into laser with remaining eye.
  34. Re: So? by Black+Parrot · · Score: 4, Interesting


    > Well, according to an article I read yesterday the MSBlast theory of the power blackout in the US and Canada isn't dead just yet. They don't think MSBlast was the reason of the blackout anymore, but that the worm slowed down and crashed monitoring systems. In that way the worm worsened the problem and didn't stop it where it could have been stopped.

    Supposedly there are "thousands" of people/organizations already working up lawsuits against that one energy company that's starting to pick up the stink. If it turns out that Blaster had anything to do with it at all, someone's going to get creamed for it.

    And you can bet that they'll go after $omebody with deeper pocket$ than whatever punk-ass kiddie it was who released it. With 50,000,000 people inconvenienced and a reported $6,000,000,000 dent in business, we're talking about a sum that would be a concern even to $DEEPPOCKETS.

    --
    Sheesh, evil *and* a jerk. -- Jade
  35. I agree by kramer2718 · · Score: 3, Insightful

    What kind of sick airline uses Windows servers to do check in and track flights/passengers. Is their IT department completely slow? They deserve what they get.

    (Disclaimer: I've flown Air Canada. The accomodations were very nice.)

    1. Re:I agree by Anonymous Coward · · Score: 0

      Besides, if they had patched their g.d. systems they wouldn't be getting hit by the cleanup worm would they? Tough shit I say! I think the RPC hole was publicized enough by Blaster that any Sysadmin on this side the Earth's crust has had more than a fair chance to patch. Most of the systems hit by this worm probably never would have got patched. When it comes to any kind of customer service, I've never considered Air Canada remotely competent -- and gee, they are hovering around bankrupcy, what a surprise!

    2. Re:I agree by Pig+Hogger · · Score: 0, Troll
      What kind of sick airline uses Windows servers to do check in and track flights/passengers. Is their IT department completely slow? They deserve what they get.
      Many years ago, Air Canada absorbed Canadian (Pacific) Airlines, which had deliberately poison-pilled it's IT systems in order to make that merger painfuller. It so happenned that the Canadian (Pacific) Airline IT guys gained control of the Air-Canada IT department, and began kicking-out the flawlessly functionning OS/2 systems that were the rule, and introduced Winblows boxen. Ever since, Air-Canada has been going down, narrowly escaping bankrupcy a few weeks ago...
    3. Re:I agree by tomhudson · · Score: 1
      poster wrote:
      I've never considered Air Canada remotely competent -- and gee, they are hovering around bankrupcy, what a surprise!
      No, they're already in bankruptcy protection since April 1st story here and lost over half a billion the last quarter.

      Three points

      1. Bleeding money like that, its no wonder that they didn't patch - they don't have the staff on payroll to do it any more.
      2. We can expect to see this pattern repeated at most airlines and other borderline-solvent businesses.
      3. On the good side - this should give the surviving companies an impetus to move away from Windows.
      Guess this is one of those 3-point plans where we CAN actually see step 2 leading to a profit, courtesy of Microsoft (who'da thunk it? :-)
  36. I predict that we haven't seen the last of this... by sllim · · Score: 3, Insightful

    This new worm, it looks to me like it is being dubbed an anti-virus.

    Most of the time I learn about something and think it is new it is not. So I won't act shocked when some /.r comes forth and cites instances of anti-viruses in the past.

    However I personally have not come across this before.
    I predict that the anti-virus will never be as prevolent as the virus, but we can expect to see them from here on out.

  37. And then what? by Felinoid · · Score: 1

    If this worm fixes the problem then it's not worse than the original worm.
    The original worm is called blaster so for the sake of lazyness and hommage to mad max I'll call the new one master.

    So master is more effecent than blaster. Probably more compact and certanly smarter. So it'll get to most of the unsecured machines before blaster dose.

    While master may be a bigger nusense than blaster it's also a one time nussence while blaster is in it for the long hall.

    So hay what's the big deal if the users don't secure there own systems master will do it for them.

    --
    I don't actually exist.
    1. Re:And then what? by AlphaSys · · Score: 1

      Your carefree attitude about who patches the systems implies YANASA, either.

      --
      Can I bum a sig? I left mine at the office.
  38. Re:Welcome to the WORM wars by Black+Parrot · · Score: 3, Funny


    > Send a worm to kill a worm!

    Two worms enter, one worm leaves!

    --
    Sheesh, evil *and* a jerk. -- Jade
  39. doesn't seem to be some kid's work by RallyNick · · Score: 1

    judging from what they do (or don't do for that matter) neither of the two worms seem to be some lifeless kid's work. they smell much more like some pissed off network/security admin(s) who wanted to slap M$. could even be the same guy twice. network slowdown is more like a side effect, not much of an issue that is.

  40. Re:Welcome to the WORM wars by Black+Parrot · · Score: 1


    > Two worms enter, one worm leaves!

    Heh, just after I clicked "submit" it occured to me that one guy in the Thunderdome was named "Blaster".

    --
    Sheesh, evil *and* a jerk. -- Jade
  41. Re:My connection sucks by Anonymous Coward · · Score: 0

    ISP is Cox HSI, i'm located in Rhode Island on the east coast. I was downloading something at about 150kbyte/sec (not my max btw), then suddenly it started to slow down, sites stopped working, aim was lagged. I power cycled my modem to reset it and it couldn't reestablish a connection, the "cable" light would blink and blink then it would reset and try again, did this for maybe 20 mins then it finally synced, but my router couldn't get an IP. I reset it again and it connected like normal and my router got an IP but nothing worked. I tried resetting a few more times, same thing. Signed on my 56k and aim wouldnt work, but sites worked, then aim worked, everything was slow (slower than normal, even for dialup). Finally about 2-3 hours later it worked.. I found out because a friend of mine the town over sent me an IM asking if my cox connection went down because his did. So I signed back on with the cable modem and its been working since (but slow, bad ping, cant tracert anything, i get all timeouts after my first 2 hops (router and a 10.x.x.x address))

  42. Worm vs. Worm - It's a Ripoff! by teamhasnoi · · Score: 5, Funny
    I got this on pay-per-view last week and it was totally fixed. MS Blaster dove off the top rope onto MS Patcher, and then kept booting him, and rebooting him. MS Patcher was like, "Huh? What?" until his manager got in the ring and slapped him.

    You couldn't tell, but I used the freeze-frame on my Beowulf cluster of Tivos and saw that there was hidden IP in Blasters hand.

    I was so pissed, I called Fight Update to complain, but the lines were all busy.

    Never again will I pay $179 for a pay-per-view wrestling match...although the upcoming free-for-all cage match between SCO, Linux, IBM, Novell, Red Hat and FSF sounds pretty interesting. I bet that PanIP will make an appearance and beat the hell out of somebody too.

    Someone always gets in the cage at the last minute.

  43. Slammer worm crashed Ohio nuke plant network by Anonymous Coward · · Score: 1, Interesting
    Slammer worm crashed Ohio nuke plant network

    "The Slammer worm penetrated a private computer network at Ohio's Davis-Besse nuclear power plant in January and disabled a safety monitoring system for nearly five hours, despite a belief by plant personnel that the network was protected by a firewall, SecurityFocus has learned."

    ...

    "The Davis-Besse incident was not Slammer's only point of impact on the electric industry. According to a document released by the North American Electric Reliability Council in June, Slammer downed one utility's critical SCADA network after moving from a corporate network, through a remote computer to a VPN connection to the control center LAN.

    "A SCADA (Supervisory Control and Data Acquisition) system consists of central host that monitors and controls smaller Remote Terminal Units (RTUs) sprinkled throughout a plant, or in the field at key points in an electrical distribution network. The RTUs, in turn, directly monitor and controls various pieces of equipment.

    "In a second case reported in the same document, a power company's SCADA traffic was blocked because it relied on bandwidth leased from a telecommunications company that fell prey to the worm.

    "Reports on the effect of last week's Blaster worm on the electric grid, if any, have yet to emerge."

    1. Re:Slammer worm crashed Ohio nuke plant network by gregarican · · Score: 1
      Mod this one way up!

      This is really interesting, to say the least. Especially if the recent blackout in the Northeast was actually due in part to placing mission critical apps on the Windoze OS. Initial reports said that the blackout was due to lightning hitting a Niagara Falls facility, but lately failures in Northern Ohio have been linked to the early problems that immediately preceeded the blackout.

      If any of this could be tied back to Micro$loth software exploits hopefully 50 million customers who lost power could perhaps swing the national attention toward two facts:

      Micro$loth software is faulty and isn't suitable for mission critical apps from a security standpoint.

      The average home user who is barely computer literate shouldn't be running Micro$loth software on their PC's if they have Internet connectivity. They should have to take courses much like Driver's Ed for getting a driver's license.

      Perhaps if folks had to take an exam before running Windoze they would at least have the sense to install a software/hardware firewall and routinely patch their shitty OS!

    2. Re:Slammer worm crashed Ohio nuke plant network by Anonymous Coward · · Score: 0

      A lot of people beleive that the power outage is related to the worm. As reported in the Globe and Mail:

      ...the problem appeared to have cascaded after the breakdown in the three high-voltage lines south of Cleveland in the area served by utilities owned by FirstEnergy.

      FirstEnergy acknowledged that an alarm that should have flashed a red warning on computer monitors when power was being lost, did not sound in its central control room.

      That warning system and the SCADA system which performs the monitoring both depend on RPC. There's been some speculation to suggest that a system admin blocked the RPC ports to protect the corporate intranet from the worm, thus causing the warning system to fail.

      The warning was visible in other locations but no one bothered to pick up the phone... possibly because they believed the control centre would already have been aware of the problem.

      There's something to be said for good old fashioned alarm bells.

  44. Windows servers by danielsfca2 · · Score: 4, Funny

    At Boston/Logan airport last Friday, I saw on a Delta departures/arrivals screen this Windows error dialog in front of the grid of flights:

    "At least one service failed to start..."

    I took a photo of it. I thought:

    - "I'm glad I don't run Windows." - "I'm glad I'm not flying Delta today."

    1. Re:Windows servers by kramer2718 · · Score: 1, Informative

      Yeah. It's amazing where you'll find Windows. For the past few days, the local public education cable channel has had a Windows login prompt misdisplayed.

      Windows is fine for games and light use, but who why would you want to do anything serious with it? Sooner or later, these companies will wise up and move to *nix.

    2. Re:Windows servers by media_whore · · Score: 3, Interesting

      You should visit New Zealand some time. I can honestly say, I have never visited an international airport terminal here where there has not been at least one of the arrival/departure screens showing 'This program has performed an illegal operation'. And I visit a fair few international airports.

    3. Re:Windows servers by BigBlockMopar · · Score: 5, Informative

      Yeah. It's amazing where you'll find Windows. For the past few days, the local public education cable channel has had a Windows login prompt misdisplayed.

      Airport FIDS (Flight Information Display Systems) tend to run Windows. I used to manage a system of a few thousand displays running a weird Continental Airlines and Infax proprietary protocol. There were two big reasons for using Windows, despite the suckage. One is that it's a hell of a lot easier to find programmers who can do custom work quickly in the Windows enviroment. The other is that Windows support for things like multi serial cards and stuff is a lot better; we often didn't have too much choice in the hardware we had to use (strange implementations of the old current loop, on 16 ports, for example... with only one supplier). Airports are very conservative, and with good reason. They really don't like change. Lots of serial cabling and repeaters where Ethernet would have done a great job.

      How about this one: The Canadian government's Office Of Critical Infrastructure Protection and Emergency Preparedness runs IIS.

      Why, given the nature of the department and (one would hope) its awareness of the threats, would they use IIS while more stable and more secure alternatives are still available?

      This is like a fire station which keeps the bin full of oily rags next to the Captain's personal collection of matchbooks from world-famous hotels.

      Looking at that site and seeing the fragile infrastructure they're using, I can't help but feel proud to be a Canadian. Jesus wept.

      --
      Fire and Meat. Yummy.
    4. Re:Windows servers by Feztaa · · Score: 4, Interesting

      Yeah. It's amazing where you'll find Windows.

      I work at a gas station, and the computer that controls the gas pumps runs on windows. IOW, if windows crashes, nobody can pump gas, and nobody who has pumped gas already can pay for their gas. It hasn't crashed on us yet (AFAIK -- I've only worked there for a month, and the station has been in service for 2 years).

      But, we have had some problems with it. One day, it kept popping up a stupid dialog saying that the computer is too hot and that if we don't cool it down fast then we'll have to shut it off. Yeah, like we're just going to turn off all our gas pumps in the middle of rush hour (the busiest time of day).

      Later that same day, it popped up with a stupid message saying that had automatically downloaded and installed updates and patches for us. Seeing that message made me cringe, I was so worried that the patch might have broken something and rendered the entire gas station useless. *shudder*

    5. Re:Windows servers by adpowers · · Score: 3, Interesting

      When I was in an airport a few days ago, I saw one of their chemical identification things (where they put that little cloth after wiping down your bag) booting up. It was running (I believe) Windows 95 (either that or 98, couldn't see the number). I felt safe knowing that national security is in the hands of Microsoft.

    6. Re:Windows servers by dardem · · Score: 2, Insightful

      I know this is off topic, but I remember seeing an Amiga boot prompt (the one with the hand holding the disk) for several days on a public/marketing station in Ireland. This was pretty cool at the time, cause the Amiga was cool. Windoze is pretty lame so seeing it on you TV is a pretty lame also.

      Gota make ya wonder....

      --

      "Ceilean Súil an ní ná feiceann..."
    7. Re:Windows servers by CurlyG · · Score: 5, Funny

      Holy shit, your gas station is running Windows and is connected to the internet??

      Please, please tell me that the pumps can't actually be controlled from the PC running the station...

      --
      You know they call 'em fingers but I've never seen 'em fing. Oh, there they go.
    8. Re:Windows servers by Anonymous Coward · · Score: 4, Funny

      Ummm... there's this thing called a handle... it controls the 'gas' coming out of the nozzle... ummmm... it's like, a handle. You know?

    9. Re:Windows servers by Anonymous Coward · · Score: 0

      I saw a Wells Fargo (i think) ATM in San Francisco showing a BSOD.

    10. Re:Windows servers by JTunny · · Score: 5, Insightful

      In my hiatus from technical employment (over now after 18 long months) amongst other things I've worked as a baggage handler.

      The clients for the baggage reconciliation system (BRS - ensures bags travel if and only if the passenger gets on the plane, implemented after Lockerbie) run on Windows 3.1!!!

      First thing I thought is, what happens if someone wiretaps the network cable? I'd guess it wasn't encrypted, or if it is, it's a 10 yr old technology, How long would it take to crack it, learn protocols and be able to wreak havoc?

      Must by archaic/vulnerable systems like that in key installations everywhere. Scary to think.

    11. Re:Windows servers by CurlyG · · Score: 1

      Well sure, but not to come over too luddite or anything, having a few thousand gallons of gas, plus pumps and assorted equipment potentially accessible by the kiddiez doesn't strike me as the most sensible idea, to say the least.

      --
      You know they call 'em fingers but I've never seen 'em fing. Oh, there they go.
    12. Re:Windows servers by krumms · · Score: 3, Interesting

      But, we have had some problems with it. One day, it kept popping up a stupid dialog saying that the computer is too hot and that if we don't cool it down fast then we'll have to shut it off. Yeah, like we're just going to turn off all our gas pumps in the middle of rush hour (the busiest time of day).

      What, would you rather it just packed up shop and died quietly?

      Later that same day, it popped up with a stupid message saying that had automatically downloaded and installed updates and patches for us. Seeing that message made me cringe, I was so worried that the patch might have broken something and rendered the entire gas station useless. *shudder*

      Since you're so worried about it, I hope you turned this feature off, then - but perhaps it's just as well, since it probably installed the RPC DCOM fix for you: right?

      Which leads me to wonder, as an earlier post did: why on earth is this system sitting connected to the Internet?

    13. Re:Windows servers by Spoing · · Score: 4, Funny
      Windows is fine for games and light use, but who why would you want to do anything serious with it? Sooner or later, these companies will wise up and move to *nix.

      [comic book guy voice] You would think that, but no, no they won't. [puts hands to face and continues to cry]

      On a dead serious note, I have personally wasted 2 hours yesterday on this new strain of the worm (it took down a customer's network that one sub-project needs -- they are SOL). Add 10 hours for the original one and it's a big block of my time over the past week...so much so, that my contract has been extended at this site to deal with the backlog multiple departments are suffering with.

      Here's the kicker; all *my* computers run Linux...yet, the network uses Windows, so the Linux systems become marginally useful even though they pur along fine by themselves.

      Even though I'm not in the IS department on this project, I do get drafted because I know something...and the IS folks are not the cream of the crop here. Some are good, though they all do too much of the 'stand of one leg...no, server is still sick...stand on other leg...nope, is it time? OK, hit the lights and get the chicken while I light the candles.'.

      You can bet that I've been pointing out that I have not had a single virus on my machines, though honestly that is a small value since most of what I do requires the damn network!

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    14. Re:Windows servers by kahei · · Score: 1, Troll


      But, we have had some problems with it. One day, it kept popping up a stupid dialog saying that the computer is too hot

      Ha! No *real* OS would ever warn about overheating! Real OSes just die!

      Later that same day, it popped up with a stupid message saying that had automatically downloaded and installed updates and patches for us.

      Ha ha! How pathetic, it automatically downloads patches when configured to do so! A REAL OS would rely on the Patch Fairy!

      See, this is a problem with putting gas station attendants in charge of computers.

      --
      Whence? Hence. Whither? Thither.
    15. Re:Windows servers by leoboiko · · Score: 3, Insightful
      It's amazing where you'll find Windows.

      Indeed. My bank's ATMs have a cool touchscreen interface. Sometime ago, I was greeted by the usual window about "illegal operation", etc. The thing then rebooted, displaying what looked like a common PC BIOS, and booted Windows 2000.

      This is a case where I think Windows is not too little, it is too much. One wonders how much this (Brazilian, once-public) bank spent with Microsoft licences and hardware when any small, light, specialized OS would do better.

      Fortunately, this is changing. At least one bank is already using Linux.

      --
      Prescriptive grammar:linguistics :: alchemy:chemistry. Stop being a nazi and learn some science.
    16. Re:Windows servers by Zro+Point+Two · · Score: 1

      Yeah. It's amazing where you'll find Windows.

      I've managed to see a BSOD on the McDonalds drivethrough screen one morning, but when I asked the lady at the window, she said that that display was running off of a different computer than what the registers use.

      --
      Zro . two

      "I come from Canada...they say I'm slow....eh?"
    17. Re:Windows servers by hdparm · · Score: 3, Funny
      Which leads me to wonder, as an earlier post did: why on earth is this system sitting connected to the Internet?

      So they can act swiftly and download patches :o)

    18. Re:Windows servers by Shardis · · Score: 4, Interesting

      "Since you're so worried about it, I hope you turned this feature off, then - but perhaps it's just as well, since it probably installed the RPC DCOM fix for you: right?"

      Which leads me to wonder, as an earlier post did: why on earth is this system sitting connected to the Internet?


      It might've installed the patch, if someone set it up that way. It's probably setup with 'net access for that reason. The clerk who seems to know better sounds like just a clerk though, and is probably (hopefully) locked out of administrative functions.

      But then, probably not. Anyone who doesn't know by now not to just automagically update without warning or testing on a system you rely on is just too incompetant to be doing the job.

    19. Re:Windows servers by Anonymous Coward · · Score: 1, Funny

      Yeah, but if its not connected to the internet, why would it need patching?

    20. Re:Windows servers by nedwidek · · Score: 1

      I was there on Saturday (and Sunday, damn Delta, never flying with them again) and the dialog was warning them about critical updates.

      --
      Post anonymously - For when your opinion embarrasses even you!
    21. Re:Windows servers by RackinFrackin · · Score: 1

      I remember seeing the same type of thing back in the early 90s in Montgomery, Alabama. The local cable system ran a preview guide channel on an Amiga. I learned this one day when I flipped to that channel and saw a Guru meditation number instead of the day's listings.

    22. Re:Windows servers by peterpi · · Score: 1

      Here's a tip: Take the day off every 49 days. ;)

    23. Re:Windows servers by Anonymous Coward · · Score: 0

      Looks like billy's astroturfers have made it into the moderation system.

      The parent post makes a VERY good point. The poster's history does not suggest that he is recycling this argument simply to start a flamewar. The troll mod is undeserved. See ya in M2!

    24. Re:Windows servers by Anonymous Coward · · Score: 2, Interesting

      National security would be in the hands of whoever wrote the software in use to do the actual scanning - not the host operating system.

      It doesn't matter whether you run a Microsoft OS or a flavor of Linux (or any other operating system). In the end, it is the software (in combination with the hardware) that does the actual scanning that makes the real difference.

    25. Re:Windows servers by Quaryon · · Score: 2, Funny

      It's times like these that we need a "+1, Worrying" moderation level..

      Q.

    26. Re:Windows servers by dukerobillard · · Score: 5, Insightful
      How about this one: The Canadian government's Office Of Critical Infrastructure Protection and Emergency Preparedness runs IIS.

      It's just their website, dude. It's not some mission-critical thing.

      This is like a fire station which keeps the bin full of oily rags next to the Captain's personal collection of matchbooks from world-famous hotels.

      No, it's as if a fire station's PR firm had the oily rags and matches. Well, if fire stations had PR firms, I mean.

    27. Re:Windows servers by mnmn · · Score: 1

      When I heard Air Canada is running all their systems on Windows, I immediately thought I should send out letters as a consultant to their CIO offering a Linux replacement for simple servers. Depending on what adapters and IO cards they're using, I believe I could switch their entire structure at least here in Toronto.

      There are plenty of Linux techies here in Toronto wandering about unemployed while the companies are investing in Microsoft.

      --
      "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
    28. Re:Windows servers by meatspray · · Score: 1

      With a little luck it's just connected to an intranet, maybe a little firewalled.

      I woun't say it's not possible that it's open and inviting all 133t d000dz to come in and play havoc, but it sounds like it might be a commercial solution and hopefully they have at least put in the most trivial of security checks.

      if not, no gas 4 uuuuuuuuu

    29. Re:Windows servers by gristlebud · · Score: 5, Interesting
      Our company borrowed one of those machines from the manufacturer to determine its effectiveness at measuring trace explosives in soil for environmental cleanup.

      Because we wern't a paying customer, we were sent the company's test-mule where all the new developments were tried before going into production.

      The machine used a lightly modified Windows 98 installation as it's OS. Security was non-existant, as any idiot (me) could go in and monkey with passwords, workgroup settings, and file locations. (I did this to get it to talk to our network for backup) I was concerned about this at first, until I realized that these devices

      weren't used with mice or keyboards

      and typically had armed guards nearby who took a dim view of people monkeying with the hardware

      As far as the installation of windows, we used it for 3 months straight, with absolutely no crashes whatsoever. The only time it was rebooted was when it was shut down for the weekends.

      --
      OK...
      I can do this. I am, after all,
      a superhero!
    30. Re:Windows servers by haruchai · · Score: 1

      I'm one of those unemployed techies and would love to be involved with any project migrating from Windows to Unix.

      --
      Pain is merely failure leaving the body
    31. Re:Windows servers by Scrameustache · · Score: 1

      Even though I'm not in the IS department on this project, I do get drafted because I know something...

      "This man knows too much..." -SCO

      --

      You can't take the sky from me...

    32. Re:Windows servers by Woy · · Score: 1

      Insightful.

      --
      "If God created us in his own image we have more than reciprocated." - Voltaire
    33. Re:Windows servers by jlrobins_uncc · · Score: 1

      Philadelphia seems to use OSX boxes all synched to a VNC server. Saw a pair of 'em get rebooted lateley during a long layover last week.

    34. Re:Windows servers by Pig+Hogger · · Score: 0, Flamebait
      There are plenty of Linux techies here in Toronto wandering about unemployed while the companies are investing in Microsoft.
      Well, if you're a Linux guy who calls giving monet to Microsloth "investing", it's no wonder you're unemployed...
    35. Re:Windows servers by hendridm · · Score: 1

      > How about this one: The Canadian government's Office Of Critical Infrastructure Protection and Emergency Preparedness runs IIS.

      Ehh, it's a government agency. They merely exist to spend money and employ people. When I worked at Uni, lots of things happened there that would never fly in the business world (well, maybe at Worldcom). Hint: They cancelled the dialup pool (which lots of people used and enjoyed) because they were in a budget crunch and couldn't afford it anymore. Meanwhile, a stroll down computer services reveals several Herman Miller Aeron chairs and the Help Desk using a 52" plasma screen to display the weather. Oh yeah, and I saw at least two of those digital marker boards with doodles and cartoons on them.

    36. Re:Windows servers by hdparm · · Score: 1

      You never know with windows.

    37. Re:Windows servers by Hatta · · Score: 1

      Heh yesterday I saw the community college cable station had the old GL cube/spikey ball screensaver on it.

      --
      Give me Classic Slashdot or give me death!
    38. Re:Windows servers by checkyoulater · · Score: 2, Informative

      where there has not been at least one of the arrival/departure screens showing 'This program has performed an illegal operation'. And I visit a fair few international airports.

      Just because the displays use Windows doesn't mean anything. It was probably easier for whoever developed the system to develop it on Windows. For all you know it could be getting all of the data from a Linux server. I have seen other cases where Windows is only used as the front end. Banks, for example. PC Financial uses Win2k workstations that connect via IBM's client access to an AS/400. The workstation might crash but it doesn't do a thing to the server.

      --
      Is that a real poncho? I mean, is that a Mexican poncho or is that a Sears poncho?
    39. Re:Windows servers by Anonymous Coward · · Score: 0

      Keep in mind that ATM manufacturers were traditionally using OS/2 -- so they are used to paying lots of money for a large, bloated OS.

      Apparently the software needs all sorts of mainframe communication drivers, and that's the main reason it's hosted on a 'real' OS.

    40. Re:Windows servers by Mr.+Bad+Example · · Score: 5, Funny

      Holy shit, your gas station is running Windows and is connected to the internet??

      "Regular, midgrade, premium...CowboyNeal? The hell?"

    41. Re:Windows servers by BigBlockMopar · · Score: 1

      When I heard Air Canada is running all their systems on Windows, I immediately thought I should send out letters as a consultant to their CIO offering a Linux replacement for simple servers. Depending on what adapters and IO cards they're using, I believe I could switch their entire structure at least here in Toronto.

      Heheh... first off, you might be underestimating the complexity of airport systems. But you haven't seen the Air Canada computers, have you? Remember that AC is essentially a Crown Corporation... neither efficiency or intelligence are prerequisites their employees, though I feel badly for the front-line customer service people who have nothing to do with the airline's problems.

      In Terminal 2, on the Domestic Departures level and area, there is a little hallway and a door. That little door leads you into an antique computer museum where the power lights are still lit, and the curator seems to be Dr. Emmett L. Brown.

      It would take you weeks to figure out the cabling in that room, let alone the undocumented production code and weird structures of databases.

      There are plenty of Linux techies here in Toronto wandering about unemployed while the companies are investing in Microsoft.

      I know. It's horrible.

      --
      Fire and Meat. Yummy.
    42. Re:Windows servers by BlowChunx · · Score: 1

      ...tragic gasoline fight accident ...

    43. Re:Windows servers by uberdave · · Score: 1

      Hmmm... Handheld computer: Check, wireless access: Check, Non-secure OS running pumps: Check... FREE GAS!!!

    44. Re:Windows servers by Anonymous Coward · · Score: 0

      The Connecticut DMV still uses Windows 3.1. At least they don't have to worry about the blaster worm :o

    45. Re:Windows servers by Feztaa · · Score: 1

      Holy shit, your gas station is running Windows and is connected to the internet??

      I don't know much about the setup. It's not like I can just minimize the POS system window and start browsing slashdot when there's a line of customers out the door, waiting to pay for their gas. All I know is that it popped up saying it installed updates, I don't know anything about the network setup there at all. I'm just a clerk, after all.

    46. Re:Windows servers by Feztaa · · Score: 1

      What, would you rather it just packed up shop and died quietly?

      The point was, we didn't shut it off, and it didn't die. So the warning was pretty pointless.

      Since you're so worried about it, I hope you turned this feature off

      Not my business -- I'm not the admin.

    47. Re:Windows servers by rthille · · Score: 1

      Just before 2000-01-01, well maybe around 1999-06, my wife got a new credit card that expired after 2000-01-01. She rebooted a few gas pumps with that card :-)

      --
      Awesome furniture, accessories and cabinetry in Santa Rosa, CA: http://humanity-home.com/
    48. Re:Windows servers by MegaLung · · Score: 1

      Yeah, thanks for posting this...it'll make the FBI screen someday. Hopefully before a disaster.

    49. Re:Windows servers by Anonymous Coward · · Score: 0

      PR Boss: We need some good publicity if we're to keep the municipal contract.

      BPFH (Basterd Publicest From Hell): All right, what do we need?

      PR Boss: Saving city hall wood be a good start...

      BPFH: Goes off to get matches....

    50. Re:Windows servers by Jucius+Maximus · · Score: 1
      "Indeed. My bank's ATMs have a cool touchscreen interface. Sometime ago, I was greeted by the usual window about "illegal operation", etc. The thing then rebooted, displaying what looked like a common PC BIOS, and booted Windows 2000."

      I am surprised by this. Most North American ATMs (assuming you live in North America that is) use OS/2 as their OS. No kidding. (I have worked at a major bank so I was privy to some of this knowledge.)

    51. Re:Windows servers by Syberghost · · Score: 1

      Just because the displays use Windows doesn't mean anything. It was probably easier for whoever developed the system to develop it on Windows. For all you know it could be getting all of the data from a Linux server.

      So what? Doesn't make it hurt any less when the Windows boxes all go away.

      We (FedEx) have a project that uses lots of Windows boxes for just one part of the process, and feeds it all into UNIX servers.

      It only took a few forgotten Windows servers (my team isn't responsible for the Windows boxes) to bring the whole thing to its knees. As usual for these worms, even a small handful of boxes sitting unpatched on somebody else's subnet can swamp yours with traffic, and having a firewall makes it WORSE if you get hit with the "good" worm.

      Whomever wrote the first worm should be shot; whomever wrote the "good" worm should be drawn and quartered.

    52. Re:Windows servers by Anonymous Coward · · Score: 0

      but who why would you want to do anything serious with it? Sooner or later, these companies will wise up and move to *nix.

      They probably considered a *nix, had their HR interview candidates, but the smell was overpowering, leading them to fall back on the dull, albeit well-scrubbed, Windows drones.

    53. Re:Windows servers by riko_at_anubics · · Score: 1

      It's charity. This way on NewYear's Day some kiddie can make the station explode, thus saving money. :-)

      --
      I don't want to start any blasphemous rumors but I think that God's got a sick sense of humor. DM
    54. Re:Windows servers by Anonymous Coward · · Score: 0

      these devices... typically had armed guards nearby who took a dim view of people monkeying with the hardware


      1) Substitute "minimum-wage-paid federal employees" for "armed guards, and I'd agree.

      2) How hard would it really be to Social Engineer these people? Show up with a laptop, a few spare circuit boards poking out of a worn-looking tool bag and a clipboard, and they'll mosy likely let you poke around the innards as much as you like. Hmm- sounds like a good job for an investigative journalist....

    55. Re:Windows servers by Anonymous Coward · · Score: 0

      "One is that it's a hell of a lot easier to find programmers who can do custom work quickly in the Windows enviroment."

      Of course, programmers doing custom work quickly is the source of about half our problems (the Windows environment supplies the other half).

    56. Re:Windows servers by Anonymous Coward · · Score: 0

      I was in NYC a few months ago and the Toys'rUs on Times Square had a windows error message on the marqee! I think maybe Microsoft is trying to market win2000 as a toy now?

    57. Re:Windows servers by Feztaa · · Score: 1

      Ha ha! How pathetic, it automatically downloads patches when configured to do so! A REAL OS would rely on the Patch Fairy!

      Got the warning again today, but I read it more carefully just for you.

      The gist of the message was that it wanted us to reboot to complete the update, otherwise the system might be unstable. Yes, we'll just reboot the computer, that'll work. No, downtime is not an option (except at nighttime, when we're closed).

      I don't trust any OS that will just go and make itself crashy without any warning whatsoever, when 100% uptime is an absolute must.

    58. Re:Windows servers by BigBlockMopar · · Score: 1

      Of course, programmers doing custom work quickly is the source of about half our problems (the Windows environment supplies the other half).

      Absolutely dead right. Unfortunately, quick custom programming is often required, because airports have so many levels of bureaucracy interconnected by so many computer systems and databases and operating systems... fortunately, the computers communicate with each other a lot easier than the people. "By the way, we're changing this aspect of the protocol tomorrow..."

      --
      Fire and Meat. Yummy.
    59. Re:Windows servers by darkmeridian · · Score: 1

      I was hanging out in Atlantic City over the weekend and saw a slot machine being serviced. It ran Windows 98. Saw the bootup screen and everything.

      It would seem stupid to put so much money in control of such a "lightweight" OS but then I realized that there is no way a typical end-user can subvert the system. And the slots have to be on some kind of network to allow progressives, so abnormalities can be detected and rectified. But still, Win98. Who would have thought?

      --
      A NYC lawyer blogs. http://www.chuangblog.com/
    60. Re:Windows servers by CurlyG · · Score: 1

      I've heard - reliably - of similar setups with networks of 20-30 such slots in each venue all hooked up to an MS DOS machine (no shit) that has the actual connection to the central server for the region (dealing with many hundreds of venues).

      The thing is, as you point out, the hackability of the OS doesn't really come into it too much. It's a fairly closed system, and well enough designed to withstand bits of it crashing, as I've personally experienced once or twice. No BSODs so far though, and sadly no free payouts - it's always been network-related crashes of some sort, which you may or may not find surprising...

      --
      You know they call 'em fingers but I've never seen 'em fing. Oh, there they go.
    61. Re:Windows servers by Reziac · · Score: 1

      Are you suggesting "+1, Worrying" be applied to the post, or to the poster? ;)

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    62. Re:Windows servers by Reziac · · Score: 1

      Wasn't it OS/2 v1.something? but IIRC it's just the kernel, not the whole OS.

      I'd assume that an ATM running Win2k is probably using a stripped down/embedded build, not much more than the kernel. Meaning not very different from using OS/2.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    63. Re:Windows servers by Anonymous Coward · · Score: 0

      "Ha! No *real* OS would ever warn about overheating! Real OSes just die!"

      Correct, a "real OS" wont care about temp.
      Real hardware would be paying atention and deal with it.

      Judging from the serer hardware I've worked with.

  45. Is anyone else getting the mental image by mcc · · Score: 4, Funny

    ...of two huge monsters battling over Tokyo and knocking over buildings in their fight while the puny sysadmins in their tanks futilely try to hurl patches, and one of the huge monsters is Good and one of the huge monsters is Bad but no matter becuase even if the good one wins, Tokyo is getting stomped flat either way?

    Okay, I think I've just proven that I've been awake too long. Goodnight..

    1. Re:Is anyone else getting the mental image by Hittite+Creosote · · Score: 1

      Not with worm vs worm. I have more an image of them firing wildly at each other with bazookas, grenades, sheep and exploding old women.

    2. Re:Is anyone else getting the mental image by HaveNoMouth · · Score: 1

      Yes. Good analogy. It also reminds me of that passage in The Diamond Age that describes how humans have to breathe through handkerchiefs because the air is full of the swirling dusty detritus of a trillion warring nanites killing each other.

  46. Hopefully... by Daemis · · Score: 1

    ...the guy that wrote this blaster-patching worm wasn't trying to use this as a way to get hired...

  47. Block it at the switch/router - by Anonymous Coward · · Score: 0

    Most of the traffic is generated by the worm shooting off all these icmp packets/requests... Just block/drop them until you can remove the worm.

    http://www.cisco.com/warp/public/707/cisco-sn-20 03 0814-blaster.shtml

  48. This is not funny any more.. by tuomoks · · Score: 1

    I usually tolerate some spam or virus e-mail but this starts to be annoying. And, please, don't bounce !! The mails are not coming from address that is in header reply - it's FAKE !! I'm getting ( only some but.. ) bounces. It's not too difficult ( look all the mail trace ) to see that the sender is not the domain that is in header, please !! AND, yes, they are coming from MS servers - haven't yet seen any other. Doesn't prove anything but.. have a nice day.

  49. Couple of things - train crashes etc. by skinfitz · · Score: 5, Interesting

    Firstly during Code Red it got blamed for Internet slowdown, until someone realised that some major net cables were damaged in a train tunnel fire that later turned out to be the real reason.

    Secondly, lots of people are (hopefully) going to be scrabbling for WindowsUpdate for patches which will also add to the bandwidth being consumed.

    1. Re:Couple of things - train crashes etc. by Shardis · · Score: 1

      Wow, insightful? Hardly.

      You know, for a network admin, it's pretty trivial to be able to tell the traffic that's downloading the latest MS patch from the traffic that's incessantly trying to scan for uninfected hosts to infect.

      Just thought you'd want to know.

    2. Re:Couple of things - train crashes etc. by skinfitz · · Score: 1

      Wow, insightful? Hardly. You know, for a network admin, it's pretty trivial to be able to tell the traffic that's downloading the latest MS patch from the traffic that's incessantly trying to scan for uninfected hosts to infect. Just thought you'd want to know.

      Another stunning interjection.

    3. Re:Couple of things - train crashes etc. by Shardis · · Score: 1

      Okay, so the "Wow, insightful? Hardly." was over the top. My apologies on that score... that did come off as rather trollish and arrogant.

      Some people here aren't technical to the level of knowledge I mentioned though. I was just meaning to point out that the traffic going to "windows update" could be relatively easily discerned and filtered out and really shouldn't be counted as bandwidth being consumed by the worm itself. At least in my (Now I guess not so) humble opinion. :)

    4. Re:Couple of things - train crashes etc. by skinfitz · · Score: 1

      Some people here aren't technical to the level of knowledge I mentioned though. I was just meaning to point out that the traffic going to "windows update" could be relatively easily discerned and filtered out and really shouldn't be counted as bandwidth being consumed by the worm itself. At least in my (Now I guess not so) humble opinion. :)

      ...which was my point entirely - people will be scrabbling for WindowsUpdate thus consuming extra bandwidth. My original point is that it's easy to blame a worm for everything when sometimes there are other more simple explanations.

      For example - major power cuts like the US has seen recently (regardless of possible cause) network gear is going to be off for a while causing traffic to reroute. This could also contribute to a perceived "slow down".

  50. We have yet to see a bad one! by CB-in-Tokyo · · Score: 3, Insightful

    So far, we rarely see a truly malicious worm or virus. Most of what we see are certainly annoying, can be expensive to clean, and cost businesses in terms of downtime, network slowdowns and data loss, however, they could be a whole lot worse. The worst one I remember is Chernobyl that would flash anything in your computer that was updateable from your video card to your Mainboard leaving you with a (figuratively) smoking lump of useless, twisted metal.

    We are always finding out about vulnerabilities. This one obviously existed since the beginning of time since it is exploitable on all post 3.1 versions of windows. If someone years ago had made a worm that infected systems slowly, so as not to draw attention, and then in a given time frame was really destructive such as chernobyl, we could end up having real problems on our hands.

    These worms that make us find and patch these holes, without wiping our systems out, are costly, yes, and annoying yes, but they are also protecting us from the really malicious ones, by making us all more aware, and ensuring that steps are taken to prevent. I am not just talking about the cleanup worm, but also MSblaster. It doesn't destroy anything, but it makes us protect ourselves, makes us develop an immune system.

    I am not saying I like them, and in my work I am the one responsible for protecting our offices, and cleaning up if something were to get through but I would rather be protecting from MSBlaster, than something really nasty.

    1. Re:We have yet to see a bad one! by AlphaSys · · Score: 1
      These worms that make us find and patch these holes, without wiping our systems out, are costly, yes, and annoying yes, but they are also protecting us from the really malicious ones, by making us all more aware, and ensuring that steps are taken to prevent. I am not just talking about the cleanup worm, but also MSblaster. It doesn't destroy anything, but it makes us protect ourselves, makes us develop an immune system.

      I am not saying I like them, and in my work I am the one responsible for protecting our offices, and cleaning up if something were to get through but I would rather be protecting from MSBlaster, than something really nasty.


      First, the worms shouldn't be making you find and patch the holes... you should've already known. Second, you better not just be defending against these lame automated attacks. They are the least of your worries. The dedicated, thinking intruder is much more skillful, and C|Net won't be warning you about his modus operandi in the same kind of detail. And there's no patch system for him. You're gonna get schooled one way or another... either by choice or by force.

      --
      Can I bum a sig? I left mine at the office.
    2. Re:We have yet to see a bad one! by CB-in-Tokyo · · Score: 1

      "The dedicated, thinking intruder is much more skillful, and C|Net won't be warning you about his modus operandi in the same kind of detail."

      You are absolutely right. This exploit has been around for a long time and has been used to break many a system. As long as these exploits exist, the dedicated intruder is going to own you. These exploits will always exist under closed source systems.

      Regardless of what you think should be making you find and patch the holes, the internet is populated with people who do not know the first thing about doing this. Most people will only get this education is motivated to.

    3. Re:We have yet to see a bad one! by Cardbox · · Score: 1
      Any virus/worm that causes visible damage is relatively benign because you can see that it's there, and the more violent an effect it has on your system, the less harmful (in system terms) it really is.

      After all, in human terms, which virus is more dangerous? Lassa fever, or HIV?

    4. Re:We have yet to see a bad one! by AlphaSys · · Score: 1
      CB:

      I agree that there are many unwashed out there, but you missed the important part of what he said...

      ...in my work I am the one responsible for protecting our offices, and cleaning up if something were to get through...

      He needs to either step up to that responsibility or else relinquish it to someone who will. I was simply trying to make that clearer for him. That's what I meant when I said "by choice or by force".

      --
      Can I bum a sig? I left mine at the office.
    5. Re:We have yet to see a bad one! by Anonymous Coward · · Score: 0
      I agree. The whole msblaster worm and all these email viruses are TAME. Imagine that on the first infection by MSBLAST that it erased every god damned file on the users' hard drive. Maybe it would keep the \Winnt directory around so it could keep itself running trying to infect others. Maybe instead of erasing the files it would overwrite their contents end-to-end with garbage so you would have to go through every single file to see if it was ruined.

      What if it had flashed your bios? Hell what if it just turned on the bios password, 99% of users wouldn't be able to figure out how to get past that one.

      I'm not giving the worm writers any credit here, but they could have done a LOT worse damage. Think of every system you had to clean MSBLAST out of and patch... imagine if instead you got called to figure out that every one of those machines had all their files removed.

  51. Flooded by ARP here by r6144 · · Score: 1

    My linux box receives 10kB/s worth of packets even when idle (ordinarily this number is less than 1kB/s). Ethereal says that most of them are ARP packets, the rest are pings and port 135 requests. Guess they are related.

    1. Re:Flooded by ARP here by Anonymous Coward · · Score: 0

      My Cable Modem TRX light currently blinkenlights like I'm downloading a new ISO, and the root console has been getting "Neighbour table overflow" errors every so often; I guess from the damned amount of ARP packets on the network.

      Windows users; can't live with them, can't legally maim and torture them to death.

  52. Re:Reinstall by AlphaSys · · Score: 3, Insightful

    Well, considering that you can have no confidence in a system that is known to have had unauthorised remote commands executed on it, I'd have to say that might not be a bad idea.

    --
    Can I bum a sig? I left mine at the office.
  53. this is not good worm vs. bad worm. by htmlboy · · Score: 5, Informative

    this is a battle of bad worm vs. less obviously bad worm. i don't understand why nobody seems to realize that naichi is also a threat. besides the fact that it's a worm, it leaves behind a pair of services, exposing the "repaired" computer to future exploitation, next time through a more convenient tftp interface.

    is it really that much to ask people to read an advisory of how the worm works before cheering it on?

    1. Re:this is not good worm vs. bad worm. by Shardis · · Score: 1

      Cheers mate. You'd think this would be common sense.

      Anyway, anything that gains access to my machine that I don't explicitly authorize is bad freaking news to me. I can't believe that more people don't think this too.

  54. iptables rules by dmeranda · · Score: 4, Informative

    For those who run a Linux firewall between a network of Windows boxes and the Internet you should rate limit those IP echo (ping) packets. Refer to my previous posting where I showed some sample iptables rules.

    Of course my firewalls have port 135 (and a lot more) blocked. Still, it is very hard to keep out of a large network, it doesn't have to get through a firewall. But once inside it can quickly spread and then your firewall or border router will get flooded with pings. I was seeing well over 1 million pings per minute. At that rate my stateful Linux firewall was crawing on its knees as the connection tracking table filled up trying to remember all those echo requests so it could match them up with the echo responses. It didn't crash Linux, but it did render it near useless.

    The scariest thing with all these worms is thinking about what could have been. What if they actually did something much more serious? What if they throttled back on the network scanning just a bit so they didn't take the network completely down and it took longer to notice?

    1. Re:iptables rules by tres · · Score: 1

      My OpenBSD packet filtering bridge silently drops all ICMP coming into the network.

      I'm not trying to see who's packet filter is longer, but rather, point out that you can fairly easily cut down on the damage being done by blocking all incoming ICMP traffic at your packet filtering bridge/router.

      Sure, traceroute is nice, but things like this mean it's just not worth the ICMP overhead.

      --
      Notes From Under *nix: blas.phemo.us
    2. Re:iptables rules by tres · · Score: 1

      Ah I guess I'll cheeze out and reply to my own comment.

      Just for the sake of clarity--because dropping incoming ICMP just makes sense--it should say ALL ICMP traffic gets dropped at the firewall.

      --
      Notes From Under *nix: blas.phemo.us
    3. Re:iptables rules by fizl · · Score: 2, Informative

      Path MTU Discovery and Filtering ICMP

      dropping all ICMP doesn't "just make sense" without thinking of the consequences.

    4. Re:iptables rules by Shardis · · Score: 1

      Exactly, what if they actually had a payload to do something other than infect? Now that someone's conviently released yet another template for idiot script kiddies to use, how long before you think we'll see an updated variant that does this? :(

    5. Re:iptables rules by mdouglas · · Score: 2, Informative

      >...you can fairly easily cut down on the damage being done by blocking all incoming ICMP traffic at your packet filtering bridge/router.
      >Sure, traceroute is nice, but things like this mean it's just not worth the ICMP overhead.

      Dropping all ICMP traffic is a bad habit to get into . ICMP is necessary for ip fragmentation and path maximum transmission unit discovery to work properly. You will break things if you drop it.

  55. Worm battles... by Bridog · · Score: 1

    Great, now we have worm battles. So is SCO going to write a worm that finds SCO in Linux and reports back? And then someone can write a worm that overrides that and changes the code instead?

    --
    Most likely the #1 Unfunny Meta/Moderator on /.!
  56. Re:I told you so... by AlphaSys · · Score: 1

    Actually, the lazy admins are the $HIT. If the Critical Update plus a high-profile warning from no less than the US Govt (reprinted in media everywhere) isn't enough to make you consider reading the advisory, testing the patch and deploying, maybe you were an ostrich in a previous life. I get really amused when MS gets blasted for this but the GNU FTP server exploit which possibly tainted months worth of code updates only has the crowd screaming for the perpetrator's head. Truth is, in both scenarios, the admins are at fault.

    --
    Can I bum a sig? I left mine at the office.
  57. Microsoft/NSA released the new worm? by Anonymous Coward · · Score: 0

    I guess it's quite possible that either Microsoft, the NSA or another gov. agency released the new worm to test it as a virus attack counter measure.

  58. Not hydroelectric by brucmack · · Score: 2, Informative

    The article says that the virus is hindering repairs on Ontario's "hydro" system... not that it is affecting hydroelectric.

    Just another misunderstanding based on the use of the word "hydro" to mean "electricity"... it would be nice if at least news sources would stop making this simple mistake :)

    1. Re:Not hydroelectric by Anonymous Coward · · Score: 0
      You are a moron.

      The name of the company that delivers power in Ontario is called... "ONTARIO HYDRO".

      I'll let you guess why they were named that.

      Consequently, in colloquialism in Ontario it's typical to refer to "electric power" as "the hydro".

      Don't believe me?

    2. Re:Not hydroelectric by brucmack · · Score: 1

      I know exactly why they were named that... because at the time of Ontario Hydro's founding, most (if not all) energy came from hydroelectric sources.

      However, because of the fact that the name of the company was "Ontario Hydro", later on people started thinking that the term "hydro" referred to energy, since less and less of Ontario Hydro's generation came from hydroelectric sources.

      You'll notice that the name of the company you linked is "Ontario Hydro Energy", which in fact solidifies my point... they are attempting to prevent people from equating the term "hydro" with "energy" by placing the latter term on the end of their company name.

      It is also worth noting that this company basically just inherited/bought the name Ontario Hydro, as they have very little association with the original Ontario Hydro that was split up in the 90s.

      This "colloquialism" you mention must be from specific parts of Ontario, because it has never been used in any of the parts I have lived in.

      If you wish to continue with your opinion that I am a moron, proceed :)

  59. Re:My connection sucks by WebCrapper · · Score: 1

    1 a minute? I wish! Currently, due to some mailing lists I'm on, I'm grabbing about 3 a minute. Once in awhile I get lucky and a 3 min window goes by without any.

    Speed wise, I haven't slowed down too much though. I guess all the tree huggers are asleep here in OR. I'm currently at 1725/248, AIM hasn't died in hours - life is good!

    My girlfriend and I take weekend vacations where the most technology we use is the car to get to the camp site and our watches/flashlights. While we're there, we don't touch the car or anything else related to technology. I think its time for another REAL soon.

  60. just why... by mahhy · · Score: 3, Insightful

    Why would the "fix" worm be this much worse than the original? They do essentially the same thing, use the same exploit, transmit themselves the same way. The only different I can see is that the "fixer" reboots your PC once, whereas the original could continuosly reboot you PC. Why is the press making it sound (at least in this case) that this worm is worse than the original?!

    Perhaps its the worms attempt to download the patch from MS thats causing all the headaches, but the patch *IS* rather small, so I'm not very convinved on that point.

    Am I being paranoid, or overreacting or what?

    1. Re:just why... by NeuroManson · · Score: 2, Insightful

      Well, if the number of users with unpatched systems range into the millions at the most, and are ALL downloading the 30-40Mb of patches from Microsoft, AND are all spreading the worm simultaneously, then the traffic use is more than likely in the range of several thousand mangnitudes, then yes, they would do much more damage to both windowsupdate.com and the ISPs the users are using.

      --
      Just because you can mod me down, doesn't mean you're right. Shoes for industry!
    2. Re:just why... by mahhy · · Score: 1

      Well, considering the patch they speak of is *probably* the specific RPC-DCOM patch, its nowhere even near 30 - 40 MB. Its 897 KB. Less than a meg.

      I'm not 100% sure the worm *only* downloads that patch, perhaps someone else can verify/disprove that, but it certinaly sounds like it from what I've read so far.

      Also, keep in mind that that once a host is "cleared" by this worm it should theoretically use less bandwidth over time than one with the original worm that continues to look for vulnerable hosts. Maybe I've got the timelines incorrect on that though.

    3. Re:just why... by Anonymous Coward · · Score: 1, Interesting

      The fixer scans MUCH more agressively, causing much more traffic.

      It also apparently will keep this agressive scanning for a long time unless users intervene.

      It'd be nice if people put effort into stuff that would replicate over hundreds of thousands of systems.

      Dynamic scanning speed and duration based on date and how many generations old it is would be a nice start with the next renegade healer worm. Pay attention to infection attempts from other sources to help guide actions and pick targets. A remote kill for it (maybe leaving a don't reinfect cookie behind) so if it does get stupid businesses can quickly udp spray their nets with shutdown packets and be done with it.

      I think I'll go anonymous coward on this one.

    4. Re:just why... by NeuroManson · · Score: 2, Informative

      The thing is, the worm doesn't download *just* that patch, from the listing, it downloads at least 8 related and semi related patches.

      It's just a good thing that the worm wasn't patched in SP1 for WinXP, or else Microsoft itself could conceivably nuke thousands of warezed copies without even trying.

      PS: Microsoft, if you're reading this, you better give me a cut for the idea.;)

      --
      Just because you can mod me down, doesn't mean you're right. Shoes for industry!
    5. Re:just why... by gregarican · · Score: 1
      Probably because an uncontrolled visit to the Windoze Update site might require supporting patches in addition to the MSBlast patch itself. That in turn could mean tens (or even hundreds) of megs of downloads.

      Simultaneous downloads all hitting certain network segments could obviously increase latency. Add to that the fact that the damn thing ICMP scans the same IP's over and over again doesn't help either.

      If you simply look at overall Internet traffic and port activity you'll see that this one has made more of a dent than MSBlast itself.

    6. Re:just why... by Anonymous Coward · · Score: 0

      No, it downloads 1 patch. It has a ~8 different options depending on the default language of your system.

  61. I worm child I no kill you network by ratfynk · · Score: 0, Funny
    I worm child bot I need ram time feed please. Mother sick please help, send money to Worm Child P.O. Box 666 Swazilli Station Lagos Nigeria

    Me never forget you URL pay back much money.

    Thank You For Helping Worm and Mother

    --
    OH THE SHAME I fell off the wagon and use sigs again!
  62. You do realize this is Air Canada, right? by Sven+The+Space+Monke · · Score: 1

    Remember, this is the same airline that decided to solve its MASSIVE customer service and revenue problems by cutting free meals from flights. Last I heard, you are now charged $8 for 4 (pretty crappy) chicken wings.

    --
    A man who can't pronouce "nuclear arsenal" shouldn't have one -sig ends here.
    1. Re:You do realize this is Air Canada, right? by Ctrl-Z · · Score: 1


      Wow. Airlines still have meals? I haven't seen an in-flight meal since March. I must be flying the unfriendly skies. Not to mention that the last time, they showed "Bringing Down the House" on both the outbound and return flight.

      --
      www.timcoleman.com is a total waste of your time. Never go there.
    2. Re:You do realize this is Air Canada, right? by Stephen+Samuel · · Score: 0, Offtopic
      Last I heard, you are now charged $8 for 4 (pretty crappy) chicken wings.

      You've come a long way, baby...

      I've been flying since I was a baby, and an early memory was being pissed off that the Air Canada stewardesses kept on insisting on pre-slicing my steak for me...

      Steak and salad for lunch (steak just slightly pink in the middle) with fruit salad for desert. Real metal knifes and forks and plastic plates that were probably more indestructible than corningware.

      Now, I feel lucky to get a chicken sandwich in a paper bag.

      --
      Free Software: Like love, it grows best when given away.
  63. Re: So? by AlphaSys · · Score: 2

    The article he cites would be an interesting read. He should link it instead of being vague.

    The company that got hit is going to have a hard time blaming anyone beyond their own admins. MS did the same thing they do to mitigate any other risk plus did some extra public-awareness work. Anybody who didn't see this coming and at least follow the advisory's recommendations to firewall the appropriate ports... well, they weren't too concerned about their systems. I mean, c'mon, NetBIOS ports open to untrusted networks? What system that critical should be allowing that? I don't allow NetBIOS to my son's gaming machine!

    --
    Can I bum a sig? I left mine at the office.
  64. Lame excuses. by Inoshiro · · Score: 1

    "You can't usually block port 135 to all local traffic, because it has legitimate uses on MS networks"

    Ok, but this still doesn't explain why:
    The networks were Internet accesible.
    or why
    The critical parts of the network aren't patched.

    If I have a private network that I need to use insecure protocols on (NFS, SMB, etc), I will ensure that it's private. All borders will have strong packet filtering, and the address space will be a reserved one that's flagged as non routeable.

    Now, because I am a smart sysadmin, and I know that there will still be cross polination (by people getting virus email attachements, bringing in laptops, etc), I will also take the time to patch my test server, run the validation suite, and then roll the patch out to the production servers sooner than a month after the patch is released. After all, what the fuck am I being paid for?

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
    1. Re:Lame excuses. by WoTG · · Score: 1

      I admit it, you're right. And probably deserving of a few more mod points.

      In my post, I was primarily thinking about the parent post's implication that simply blocking port 135 would be sufficient protection. As you point out, systems should have been patched and critical systems fenced off better.

      As an aside, I suspect that a lot of the problems were of the DOS type. It wouldn't take many infected PC's (e.g. laptops) to flood a thin pipe. And I wouldn't be surprised if the connections to remote airports (in the case of Air Canada) were 128K ISDN. Which then leads to questions about QOS configuration on routers...

  65. Advice for future clean worm writers by Anonymous Coward · · Score: 1, Insightful

    The worm should not spread, instead it should sit on a host and if it gets attacked by the bad worm, it installs it self on the attacking host, cleans it, and remains dormant. the flaw in a worm searching for infected hosts is that even if all the bad worms are out, the worm will keep on searching for infected hosts in vain, using up network resources. a worms most dangerous feature is propagation.

    Use Bittorrent to make download of patches easy on networks. ._seg

  66. Re:[OT] Unnecessary linkage by cha0sadddddddd · · Score: 1

    um...i usualy RTFA (even the evil free reg required NYT ones),but you cant pay me to read any of drudge's blather.

    --
    Collecting data is only the first step toward wisdom. But sharing data is the first step toward community
  67. My connection is 3/4 dead by blackdropbear · · Score: 1

    Go back to dilaup where everyone on your local subnets runs an insecure ME or XP home edition box and then you will really know how sucky internet acces can get - it's almost as back as the old 2400 baud non erro corrected modem days. Though it is still slightly better than teh 300 baud acoustic coupler days.

  68. Re:Welcome to the WORM wars by ThaReetLad · · Score: 1

    Does all this talk of battling worms remind anyone else of the classic game "Worms" from the mid 90's? Incoming!!! BOOM!!!

    --
    You can't win Darth. If you mod me down, I shall become more powerful than you could possibly imagine
  69. Amiga errors by Cowclops · · Score: 1

    I used to see a black and red error screen all the time on what is now the "TV Guide" channel. (The tv programming scroller thing.) Through the magic of emulation, I later discovered this is the exact error you'd see after an amiga crash. The "red and black" screen of death so to speak. Apparently they weren't rare since i would see the channel doing that about 2 or 3 times a week.

    1. Re:Amiga errors by Anonymous Coward · · Score: 0, Funny

      It's a Guru Meditation, kind sir, a Guru Meditation. Just as if not more annoying than a blue screen of death.

    2. Re:Amiga errors by Anonymous Coward · · Score: 0

      You are mistaken, kind sir.
      The blue screen of death is DEATH ! And it's BLUE. Not a good fashion statement when talking about death.

      Guru meditation is a guru. And he's meditating !!! That's soooo much better! Must be !

    3. Re:Amiga errors by operagost · · Score: 1
      Now they don't show the crash- the scroll just stops working or the listing area is totally blank.

      I really need to buy a cable box!

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    4. Re:Amiga errors by dorsey · · Score: 1

      A few years ago, there was a local weather channel in my cable lineup. This channel was run entirely off of a windows 98 box that just downloaded the weather data from the NWS or something.

      Of course no one ever checked it, so every so often the weather scroller would crash, and they'd broadcast a windows desktop and an error message for a week or so before anyone noticed.

      --
      hinderfreude ('hin-dur-"froi-d&), n. The feeling of joy derived from being in the way.
  70. Wasn't this by Mark_MF-WN · · Score: 2, Interesting

    Wasn't this how viruses were "invented"? To perform upgrades? Some network admin had the bright idea of performing maintenance by having a process that jumped from system to system, updating as it went. Unfortunately, it did so in a very non-deterministic and incorrect way, and the entire network had to be taken down so that individual computers could be disinfected in isolation. Several years later, the event inspired the first research into computer viruses.

    PLEASE let me know if I've horribly botched this tale -- I'd hate to sound like a fool.

    Anyway, I'd say that the whole idea of eliminating a worm with a worm is akin to infecting someone with malaria to cure the Plague.

    1. Re:Wasn't this by Satan's+Librarian · · Score: 3, Informative
      Yep, here's one version of the tale.

      Virus history is a bit different if you follow the definition of viruses parasitically infecting files, whereas worms are self-contained and actively spread via network. Here's a paper that covers the early history of both to some degree.

  71. What puzzles me... by BorgSquirrel · · Score: 1

    ... is why, at work, we had 1300 pings/second before be asked our ISP to close off ICMP Echo Request at an upstream router, while my PF (OpenBSD rules!) has fended off only ~500 Echo Requests in the last 48 hours. Ok, at work the firewall protects 255 addresses and @home only 1, but still that math does not really explain it...

  72. And the *worst* thing is... by KingRob · · Score: 1

    That my autodisconnect no longer works cause I keep getting ping keepalives - damn those happy worms

  73. Freddy vs. Jason by Marco+Rossi · · Score: 1, Interesting

    Kinda reminds me of the movie, where 2 evil superheroes fight each other and make a lot of damage as a side effect, doesn't it?

    --
    - Marco
  74. It's not THAT good. by chrome · · Score: 4, Informative

    1) When it infects machines, 99% of the time it is unable to download the patch. This makes it pointless.

    No, I don't know why, I guess its because windows update URL has changed? All the machines that we've found with this virus have not been patched and had to have the patch applied anyway.

    2) It tries to ping every machine on it's local network as fast as it can, repeatedly. It doesn't just do a single scan then shut up til 2004 (it's expiry date) - oh no, it continually scans. Thats ok if you have 2 machines on your LAN, but when you have a huge switched lan with a few hundred or thousand hosts on a /16, thats a lot of traffic.

    I see LOTS of ARP traffic from the machines doing the scanning to hosts on the local network, and I see loads of ICMP echo-request destined for outside our network. Which I filter now.

    3) It runs as a service that isn't detected by many virus scanners, for some reason Nortons didn't find it though McAffee did. Again I have no idea why.

    The thing did a LOT of collateral damage on our network with a couple of hundred machines. I shudder to think about what kind of damage it is doing to large networks at universities etc.

    1. Re:It's not THAT good. by Anonymous Coward · · Score: 1, Informative

      The thing did a LOT of collateral damage on our network with a couple of hundred machines. I shudder to think about what kind of damage it is doing to large networks at universities etc.

      On our university network, with several thousand computers, the network has been progressivley slowing down since Sunday, and access to anywhere ouside the LAN was impossible (resolving adresses timed out every time) since Teueday morning. The network only started getting usable again a couple of hours ago when enough machines had been patched: there are still a couple of infected machines hammerng the network even now, if tcpdump is to be believed.

    2. Re:It's not THAT good. by Jmstuckman · · Score: 1

      We have about 30 infected machines. About an hour after infection, about half of them rebooted themselves with no warning. The event log showed installation of the patch. I wonder where it downloads the patch from?

    3. Re:It's not THAT good. by Nunar · · Score: 2, Funny

      So wait, I don't get it...

      Which is worse, exploiting Windoze? Or fixing it?

      "I could do a lot of stuff, if I had some money!" -Homer Simpson

    4. Re:It's not THAT good. by HTH+NE1 · · Score: 1

      1) When it infects machines, 99% of the time it is unable to download the patch. This makes it pointless.

      No, I don't know why, I guess its because windows update URL has changed?


      Imagine if it hadn't. Then the DDoS would have become a DDfS (Distributed Demand for Service), with the same result as was intended by the first.

      Yup, the Information Superhighway to Hell is laid with good intentions.

      --
      Oh, say does that Star-Spangled Banner entwine / The myrtle of Venus with Bacchus's vine?
    5. Re:It's not THAT good. by fredklein · · Score: 1

      1)...
      2)...
      3)...


      These are all resons to IMPROVE the anti-blaster worm, not get rid of it.

      The idea is sound- use a worm that uses exploit 'X' to find vulnerable machines and patch exploit 'X'. This particular implementation sucked, that's all.

    6. Re:It's not THAT good. by Anonymous Coward · · Score: 0

      I shudder to think that a network that large has not yet been patched even AFTER the MSBlast incident...

    7. Re:It's not THAT good. by chrome · · Score: 1

      Unfortunately, with windows it's very hard to *push* a patch out to a few thousand machines. You can do it with SMS (System Management Service or whatever it's called) but not everyone pays for that.

      So, usually it involves the 10 or so helpdesk monkeys to split up the 2000 machines between themselves, and work through it.

      All the while answering questions from curious users about the virus, how it spread, what damage it is doing, etc.

      That can take a few days at least.

      Then they have to hunt down the last 2 machines that are somewhere on their network that they cannot find but are still infected ... which takes a few days.

      So, I don't find is suprising that most nets hit by MSBlast hadn't been fully patched yet.

    8. Re:It's not THAT good. by chrome · · Score: 1

      Thats what they want you to think.

      Today it's a good worm that patches your machine, tomorrow it's a good worm that patches your machine and installs a very well hidden trojan that turns your machine into a packet generator for some lame IRC script kiddie.

      So-called "good" worms have a far higher potential for damage than known "bad" worms - simply because people like you will make the mistake that it's doing you a favour, and won't do the right thing when they get infected with it.

      "Oh, its a GOOD worm. That makes it ok! I won't worry about it. I'll let it just get on with what it's doing, good little wormy wormy!" *pat pat*

    9. Re:It's not THAT good. by chrome · · Score: 1

      Right.

      If the worm writer was a little bit smarter, he would have had the worm distribute the patches the same way it distributes itself - via the TFTP server.

      Ho ho ho.

      It's times like these I love running Mac OS X. Mind you, that doesn't mean I'm safe from trojans. It just means I'm safe from Windows trojans. ;)

  75. Hm...Reinfection. by Anonymous Coward · · Score: 0

    "The current round of worms are clumsy and unimaginitive. I think it's only a matter of time before we see a worm that does some -real- damage."

    Yeah! Like install Windows on your computer.

  76. BFAFH? by Doppleganger · · Score: 1, Funny

    (Bastard Flight Attendant From Hell)

    ``It's a nightmare,'' said one unidentified woman. ``The service is so bad; the management was so bad. The system is just a mess, just a mess. I had my luggage delivered to Toronto, I was told on Saturday, so I don't have anything.''

    And they're blaming it on a virus? I can see it now....

    BFAFH: "Your luggage hasn't arrived yet? Let me see..."
    *klickety-klickety*
    "It appears that it was accidently routed to the other side of the world!"
    (which makes sense, that's where it would go when the BFAFH put it on the "international flights" belt at the person's originating terminal.)

    Traveller: "What?!? How could that happen?"

    BFAFH: "Well, it's most likely due to.." *flips 'excuse of the day' calendar... hmm, this one's easy* "..a computer virus! Yes, you must have heard about it on the news, that one that is hitting all of the Windows systems? It's really quite horrible."

    Traveller: "But what am I going to do for clothes? I have a business meeting tomorrow!"

    BFAFH: "Well, the soonest we can get them here is next week. Sorry about that, have fun shopping for nice clothes in a hurry. And thank you for flying!"

  77. Incompetence by PhreakOfTime · · Score: 1

    Every time I read this sort of story, I wonder how it is that these people responsible for maintaining these networks are still employed. It seems these peoples employers are even more clueless than the twit that doesnt upgrade their systems. If your boss accepts your excuse for this occuring in your company, they are morons.

    A patch to fix this was out several weeks before this hit, as most already know. So what exactly is the reason anyone can give that this critical part of their job didnt get done in WEEKS! I had a friend of mine who works in the IT dept of a fairly large company telling me he was pissed about this because he was going to get called in early saturday when this worm hit, as they knew large numbers of their systems were infected. He was almost to the point of bragging that it was such a major situation...at which point I reminded him that he was bragging about the fact that their dept let a MAJOR hole go unfixed for almost 4 weeks.

    To drag the open source argument into this a bit, even if linux and windows had the exact same amount of vulnerabilities, which group is it that doesnt seem to have as much of a problem applying a simple 'patch'. Perhaps this is just the result of 'certification'. Where you learn enough to get some documentation saying you learned what was needed for that document...but most of these monkeys are not much better than the moron who drives for miles while the oil light is on in the car..."If the car is still running, it couldnt be that big of a problem"...

    Fix your shit people...its that simple

  78. Totally untrue! by fireboy1919 · · Score: 4, Interesting

    It's not the affending system that is attacked and destroyed, it's the systems that are attacked via DDOS through the hacked boxes using signal propagating viruses.

    Have you heard of Dalnet? The network that used to be the largest of the IRC networks? It isn't now. Four months of DDOS attacks against all it's servers brought that to a halt (and there were like 10 of them). It's come back up, but most people have moved to other networks.

    Maybe you didn't see this as a real problem because it didn't affect you, but four months can do more than merely wipe data or destroy hardware. They can take down businesses forever.

    I'd rather have the "malicious ones" destroy computers owned by users who are partially to blame for letting in viruses than destroy businesses that have no fault at all in the matter.

    On an interesting parallel: one of the most destructive viruses (real world) on the planet is Ebola. How do you think it's rate of spreading and death rate compare to AIDS? It's the slow, insideous viruses that you have to worry about, not the ones that are obvious. Not knowing that the virus is there is the best defense a virus has against innoculation or containment, which gives it more time to spread and wreak havok.

    --
    Mod me down and I will become more powerful than you can possibly imagine!
  79. real damage? by zarniwhoop · · Score: 2, Interesting

    Many posts here talk about what if worms did some *real* damage. I wonder what this could be? A worm that formats the HDD is obviously useless - how will it replicate? In order to spread, it necessarily exposes its presense and therefore it can be killed. So the max damage a worm can do is limited. Am I right in my thinking?

    1. Re:real damage? by o'reor · · Score: 1
      OK, here's a sample e-mail worm:

      --- From: your_friend@yahoo.com
      --- To: you@hotmail.com
      --- Subject: Virus alert

      WARNING ! You have just received an e-mail virus.
      To get rid of it, and to make sure noone else gets caught, do the following :
      1. Forward this message to all people in your address book.
      2. Format your hard drive.

      Simple, huh ?

      --
      In Soviet Russia, our new overlords are belong to all your base.
    2. Re:real damage? by ratsnapple+tea · · Score: 1, Insightful

      Oh, I don't know. It could scan your hard disk and send copies of all your documents to everyone in your address book, or forward all your old email. You're the CEO of a Fortune 500 company and your confidential five-year business plan gets sent to all your competitors. Your customers' credit card numbers and Social Security numbers escape into the wild. Legal documents, source code, everything. This would be damaging beyond belief.

    3. Re:real damage? by cretin999 · · Score: 1
      Many posts here talk about what if worms did some *real* damage. I wonder what this could be? A worm that formats the HDD is obviously useless - how will it replicate? In order to spread, it necessarily exposes its presense and therefore it can be killed. So the max damage a worm can do is limited. Am I right in my thinking?

      Well off the top of my head:
      Delay execution of the payload. That provides time to spread.
      Stop scanning after succesfully infecting n other machines. Minimise the chance of detection.

      Combine all the above:

      Set a flag to prevent reinfection.

      Go dormant after succesfully infecting n other machines.

      Activate on a fixed date.

      Why stop at formatting the HDD? Recursively scan the fs and zero out all (not open) files. Reboot to a sniblet of assembly that zeros out the FAT. Try and recover that!

  80. uhoh by killermal · · Score: 1
    Hardest hit was the 411 system, Air Canada...

    Does that mean we can expect to see aircrafts randomly dropping around Canada?

    1. Re:uhoh by BrainInAJar · · Score: 1

      You wish.

      Likely it's just the scheduling system or billing or the employee network or somesuch. Aircraft wouldn't be trusted with windows in place, particularly hooked up to the internet

  81. not the same way at all by commodoresloat · · Score: 1, Funny

    No; they would install *nix from scratch.

  82. So.... by Anonymous Coward · · Score: 0

    If it makes system administrators look like idiots, and does for free, and practically instantly, what would cost $5,600 and the taking of your computer to the repair shop to fix...it must be immoral and evil!!
    I guess the job market must really suck for people to see something that does good as something that does evil.

  83. Life is like fiction by Xeo2 · · Score: 1

    Am I the only person who immediatly thought og Hard Drive by David Pogue. This is creepily similar to the end of the book, except with crappy grammar...

    --
    ___ alwaysBETA.com - Hey, you've got nothing better to do.
  84. Worms are bad, but... by FireFury03 · · Score: 3, Interesting

    Worms are bad. Period. Even if the worm is supposed to be good then the damage it can do in terms of network usage, etc causes problems.

    However, vulnerable boxes do cause a lot of problems, so IMHO a better solution is for those people who care about such things to install a system on their firewall that responds to scans - if a machine scans your firewall then you look to see if you recognise the signature of the scan (i.e. the likes of Code Red, ete, have quite distinctive patterns of scanning) and then your firewall launches an exploit against that machine that is scanning you. Once exploited the system would take some action to close the vulnerability and remove the worm (i.e. turn on the auto update stuff, install whatever patches are needed, etc). After it's done that the software that you installed through the exploit would delete itself.
    This is a defense - the machine in question attacked your network so your network responded by fixing the compromised machine - no other (innocent) machines are affected by the problem.

    ISPs also need to do something to help the situation IMHO - there is no sane reason to use Netbios over the internet so this should be blocked by every ISP (I know some do already, but the vast majority still allow it).

    And remembering that 90% of home windows uses are completely clueless when it comes to security, they need to be forced into fixing their systems. The best way I can see of doing that is for all ISPs to look for scans coming from their customers - if a machine is making a lot of scans to lots of hosts all over the internet that matches the signature of a known worm, the ISP should pull the customer's entire internet connection. Infact it wouldn't be too hard for the ISP to intercept all web requests and redirect them to a website with all the patches on it. This is damage limitation - if a machine is compromised and is attempting to compromise other machines then it is essential that machine is taken off the network ASAP. If all the ISPs followed these steps then the spread of worms would be severely reduced.

    1. Re:Worms are bad, but... by TCaM · · Score: 1

      If I was writing a 'patch worm' I would also have it enable automatic updates and maybe turn on the WinXP firewall. That way the machine might stay out of the next round of worm traffic in 2 or 3 months.

    2. Re:Worms are bad, but... by kcurrie · · Score: 1

      if a machine scans your firewall then you look to see if you recognise the signature of the scan (i.e. the likes of Code Red, ete, have quite distinctive patterns of scanning) and then your firewall launches an exploit against that machine that is scanning you.

      Just great-- now I know if I spoof IP's and scan you I can have you attack whoever I wish. Defense is blackholing the box attacking you-- not attacking somebody else who may be innocent.

      If these worms just WIPED everybodies drives maybe, just MAYBE somebody would be curious AND MOTIVATED as to what they could do to prevent it next time. Right now people live for years with all kinds of viruses and worms on their boxes and don't have a clue. ..not that I would advocate mass deletions of data, but the clueless masses need SOME kind of big stick.

      --
      -- I speak only for myself.
    3. Re:Worms are bad, but... by FireFury03 · · Score: 1

      Just great-- now I know if I spoof IP's and scan you I can have you attack whoever I wish. Defense is blackholing the box attacking you-- not attacking somebody else who may be innocent.

      Ok, a valid point. But for worms that are making TCP connections (and so can't spoof the addresses since a spoofed address wouldn't be able to establish a TCP connection), this seems like a good idea.

      Either way, I'm still convinced that since 90% of home users are clueless they need to be forced into fixing their compromised boxes, and the best way of doing that seems to be to pull it off the network. This has 2 advantages - 1. It can't do any more damage to other machines, 2. If someone can nolonger surf their Pr0n, maybe they'll fix their machine.

  85. Life is like fiction by Xeo2 · · Score: 1

    Am I the only person who immediatly thought of Hard Drive by David Pogue? This is creepily similar to the end of the book, except with crappy grammar...

    --
    ___ alwaysBETA.com - Hey, you've got nothing better to do.
  86. Not just in Canada by BigBadBri · · Score: 2, Informative
    Lockheed Martin and possibly the US Navy (they may have mistaken Patcher for BLaster) are reported to have been hit too.

    --
    oh brave new world, that has such people in it!
  87. You must have that cool Godzilla game... by Anonymous Coward · · Score: 0

    Stomping on them buildings is more fun than beating up your opponents. :-)

  88. Windows Emergency Services by YaiEf · · Score: 5, Interesting

    I served military duty in the Danish Emergency Management Agency and was shocked when I saw they were implementing the entire system for reporting all kinds of disasters and emergencies (everything from tunnel fires to radiation leeks) on Windows 2000. These computers were connected to the net - and knowing the place they would probably never be updated. And even worse - it wasn't even a stripped down Windows 2000 that only ran the necessary services - it was a default (apparently unpatched) installation complete with an autostarting Messenger.

    I'm not all that great on securing Windows boxes - but that sure didn't seem right. Considering this would be the first way (and for something like 5 minutes!) to warn the local emergency services of something - which could very well be a tunnel collapse/fire/whatever where 5 minutes easily can make a lot of difference in human lives. The program that was custom-made for emergency-reporting also seemed of pretty poor quality - most likely a case of lowest bidder with noone competent seeting intelligent rules for the bidders.

    1. Re:Windows Emergency Services by Shardis · · Score: 3, Insightful

      Jeez, troll, hopefully? :P

      Granted, Win2k is prolly the best out for windows applications, but c'mon, unpatched/unstripped?

      Are you suicidal?!

      I've been having problems enough securing my Win2k machine securely, running only required (by me) services, and goddamn fully patched. Even though MS's patches break all my goddamn custom/low level apps.

      Five minutes? If you're unware on an unpatched base Win2k install on an older service pack, it takes 5 seconds to hopelessly compromise a default Win2k install if you're unlucky. :P

    2. Re:Windows Emergency Services by Pig+Hogger · · Score: 3, Funny
      (everything from tunnel fires to radiation leeks)
      Note to self: carry dosimeter to my mother's when I'll go there in case she serves me her cream of leek soup.
    3. Re:Windows Emergency Services by RexRuther · · Score: 1

      Typically the SCADA (Supervisory Control And Data Acquisition) systems for these types of facilities can be run with W2K/XP succesfully. These systems are generally for reporting and collecting information. The underlying control systems generally have more robust OS/networking.

      --
      -"The early bird catches the worm, but the late bird sleeps the most"
  89. Windows on airport displays by Anarchofascist · · Score: 5, Funny

    My wife and I were going through Dublin airport when I noticed that a number of the airport schedule display screens were going through a reboot sequence. I showed it to her : "Hey, looks like that one crashed."

    She had to point out that a more alarming interpretation of the word "crashed" may have been made by some of the other people in the arrivals area.

    --
    Once more unto the breach, dear friends, once more, Or close the wall up with our American dead!
    1. Re:Windows on airport displays by JediTrainer · · Score: 1

      LOL

      That reminds me. I was at Toronto Pearson International Airport a couple of months ago. Wished I had my camera - the ticker had a huge Dr. Watson crash dialog obscuring the arrival times!

      That dialog was there for a good hour before they figured out how to get rid of it.

      --

      You can accomplish anything you set your mind to. The impossible just takes a little longer.
    2. Re:Windows on airport displays by operagost · · Score: 2, Funny
      Good thing it wasn't a Mac- then you might have said it "bombed".

      "So, the last thing I remember is a 250 lb. guard putting his knees into my back..."

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    3. Re:Windows on airport displays by PHPee · · Score: 2, Informative

      While at the airport about 2 months ago, I noticed one of the display terminals had blue screened. I was rather delighted, so I snapped a few pics before airport security noticed.

  90. Which is why... by Kjella · · Score: 1

    ...we get programs saying "this program can only be run on Windows X", I saw one recently that refused to install a program under WinXP (was made for WinNT). Since it is downloading an official patch, I assume the patch will not run on any systems it can't patch properly.

    On a worst-case scenario, Microsoft could simply move the file and the worm is dead. But I don't think the problem you're referring to would have been big at all....

    Kjella

    --
    Live today, because you never know what tomorrow brings
  91. Reminds me of something... by Bas_Wijnen · · Score: 1, Funny

    This reminds me of something I read back in 2000 :-)

  92. Usual high standard of reporting, I see by Rogerborg · · Score: 2, Insightful

    There is absolutely no evidence that Welchia is worse than Blaster, as a cursory reading of the linked article would reveal to anyone who passed the fourth grade.

    If you're unpatched, you either get Welchia, or you get Blaster. They both hose your network. If you're too stupid to block the ports and apply the patches, then you're going to get one or the other.

    Go on, pick one. Not that it makes any difference. Welchia isn't worse than Blaster. Sure, it opens a port, and everyone is assuming (why?) that this is a back door, but as long as you're unpatched and your 135 port is open, arbitrary code can be run on your box anyway, so how does Welchia make that worse?

    Lies, damn lies, statistics, Slashdot reporting.

    --
    If you were blocking sigs, you wouldn't have to read this.
    1. Re:Usual high standard of reporting, I see by gregarican · · Score: 1
      Actually the only detriment of Welchia is hogging Internet bandwidth. Blaster, OTOH drops off its initial payload via tftp, which then can allow other trojans to be dropped off as well.

      To me I would think that Blaster would be more potentially dangerous, but agreed. Anyone with half a brain would block port 135 either on their PC, their router, or by calling their ISP for assistance.

    2. Re:Usual high standard of reporting, I see by Large+Green+Mallard · · Score: 1

      Australia's academic research network, AARNet, is currently reporting 80Gps outbound ICMP traffic from Welchia. In order to stop the country from getting saturated from this, most local peering points are temporarily blocking ICMP.

      Sorry, what was that about Welchia not being worse than Blaster?

    3. Re:Usual high standard of reporting, I see by gregarican · · Score: 1

      Checking the Internet Traffic Report site it appears as if Australia and Asia are both crawling. Don't know if this is entirely due to the Welchia worm, but blocking incoming ICMP packets on external interfaces is something I employ as a rule.

    4. Re:Usual high standard of reporting, I see by Rogerborg · · Score: 1

      And they know it's from Welchia and not Blaster beeeeecaaaaause...?

      --
      If you were blocking sigs, you wouldn't have to read this.
    5. Re:Usual high standard of reporting, I see by Large+Green+Mallard · · Score: 1

      because prior to the release of Welchia they had a baseline from Blaster? :)

    6. Re:Usual high standard of reporting, I see by Rogerborg · · Score: 1

      And Welchia infects hosts that Blaster can't beeeecaaaaause...?

      If you're pulling these figures out of your fat hairy arse, as I strongly suspect, then welcome to the wacky world of Slashdot journalism. You should apply for a job here.

      --
      If you were blocking sigs, you wouldn't have to read this.
    7. Re:Usual high standard of reporting, I see by Large+Green+Mallard · · Score: 1

      Forgive me for merely reporting that which is being reported by AARnet, they only provide internet access to several million hosts in Australia.

  93. Re: So? by joeykiller · · Score: 2, Informative

    I didn't link to the article because it's in Norwegian. But if you can read Norwegian, here it is.

    This article is based upon another article from the danish newspaper Jyllands-Posten, but I'm unable to locate the article on their web site.

  94. Re:My connection sucks by Espen+Skoglund · · Score: 3, Insightful

    And to make matters worse, you get 1 mail a minute from some remote daemon telling you that there is a virus in a message which is apparently from you. Mail administrators who set up such auto-replies shoot be taken out and shot.

  95. Why are airline systems online???! by Viol8 · · Score: 1

    Given the possibly sensative nature of the data stored on them and the risk of viruses etc

    why oh why are these airline checkin systems connected to the internet anyway??? Why don't they at least use VPN?? Sorry , but this smacks of
    utter stupidity to me. You wouldn't expect your bank to have all its client account computers connected , why don't airlines follow
    their example??

  96. This IS exactly why (-666, possibly flamebait?) by Shardis · · Score: 1

    Okay, I'm hopelessly drunk and you're (supposedly) a coder that should know better.

    I mean, just cause a system doesn't have a sysadmin... In the last day I've spent a total of about an hour getting @50+ users booted off (or at least having their internet connections temporarily severed) my home ISP's subnet(s). My fucking logger couldn't properly keep up with all the traffic this was generating!

    With all the emulated and specialized systems out there, can you guarantee that any code you write will run properly on all systems?

    Of course not. If you believe that, you're hopelessly naive and shouldn't be allowed near a compiler or interpreter.

    Believe it or not, I have actually looked into this (and I'm hosed, find sources yourself...), but almost all of the supposedly "beneficial" worms/virii out there have caused more problems or at least as many problems as whatever it was they were trying to do or fix!

    Whoever the idiot is that distributes something like a "clean up worm" deserves as much federal "pound me in the ass" prison as any of the other virus writers out there that have gotten such sentances...

    "The road to hell is paved with good intentions."

    "Ignorance is no excuse for fucking up and completely hosing some random stranger's system."

    That last platitude is mine. ;)

  97. I agree but... by Lispy · · Score: 1

    Well, I agree.
    But then again thanks to the "net send" messup the average user clicks away on reflex whatever pops up on his screen:
    - "I want to secure your box clicke here!"
    - "I want to help you make Ca$h on the web!"
    - "I want to enlarge your penis!"

    Sigh, noone would trust a real, nice, viruscleaning worm anymore.

    cu,
    Lispy

  98. whilst we're at it... by RMH101 · · Score: 1
    ...i've had a little light on my dashboard saying SERVICE pop up a few thousand miles ago. the car's making funny noises and there's a big cloud of black smoke that follows me around. do you think something might be wrong?

    +4 Interesting? FFS, people...

  99. Re:Socialism is death by Anonymous Coward · · Score: 0

    hahah ill remember that when you smash your car up and need cutting out,or when you house is burning down around you, hope you got your chequebook handy

  100. T's by 3terrabyte · · Score: 1

    Didn't they learn anything from the Terminator series? SkyNet is not the answer.

    --

    Why are there only 19 people folding@home for slashdot?

  101. Worm Vs. Worm by zarathustra93 · · Score: 2, Interesting

    I don't care what the intent was on this anti-worm worm. I have one sales guy in Australia right now that somehow managed to get *both* worms on his laptop- despite the fact that I sent him instructions ahead of time on how to patch his system and ensure that his virus definitions were updated. Now he's expecting me to help him out despite the fact that he cannot connect to our VPN, and that he's 12 hours ahead of us.

    Good Samaratain worm my ass- this one is just as big a pain as Lovesan was.

    It'll be interesting to see how this impacts the future of worms and virii though.

  102. No sympathy by Doug+Neal · · Score: 1

    I have no sympathy for any one or any company that's been hit by this. The patch for the exploit was available for ages before the worm was released. If anyone's systems are vulnerable it was no one's fault but their own, and especially after all the windows worms and viruses that have come before this one, you'd have thought people would learn by now...

    In fact I'm finding the whole thing rather amusing :)

  103. I wish I had mod points by FreeUser · · Score: 1

    If you want to help people, write your firewall activation and configuration program as a tool that allows the user to control it and distribute it freely on a website. Advertise it. If it doesn't suck, people will use it and you'll help make the internet more secure. Popular magazines might even recommend it as a really easy fix for security, and you'll help even more people. And, if you screw up, you can fix the bugs in the next version and provide support. Added bonus - the police and corporate lawyers won't be hunting you.

    I wish I had moderator points today. This is one of the most insightful posts I have seen on this subject today.

    I say this as one who doesn't really have a problem with the 'white-hat' worm (assuming it really is white-hat, and not just a more subtle attack waiting to happen, which those open ports might well represent), and any damage it does cause could reasonably be considered collatoral in a battle to secure a system the vendor and user alike are either unwilling or too incompetent to secure, and I do find the argument that your autonomy over your own system ends the moment it attacks my network to be a compelling one in some respects.

    Nevertheless, your advice, and your stance on this, makes a whole hell of a lot more practical and ethical sense: spend your energy writing software that fixes (or perhaps detects and fixes) security flaws such as this one in a manner that educats and empowers otherwise helpless users, and distribute it freely. Put your energy into something others can contribute to and improve upon, something that will allow you to receive the recognition you deserve, rather than become another hunted felon.

    Excellent advice, and it trumps the pro v. con 'good-guy' worm argument completely, whichever side of that debate one stands on.

    --
    The Future of Human Evolution: Autonomy
  104. Just as long as... by Anonymous Coward · · Score: 1, Funny

    The collection of worms/virii don't go and infiltrate high-end physics labs, change signs on equations and cause Peter Weller and company to lose out on their 5 year mission to save the Earth from destruction...

  105. W2K Service Pack 2 by b1t+r0t · · Score: 3, Insightful
    The patch for this exploit under Windows 2000 requires Service Pack 2 be installed first. I know that all the downloading for the patch is causing these network problems, but just assume for a moment that the patcher worm gets to a W2K system that has never had a Service Pack upgrade. If it's not perfectly written, it'll download the patch, try to install it, then reboot the computer, right?

    So what if it's sitting there saying "This patch requires Service Pack 2", and the worm reboots? The result: a still unpatched system! Even if the worm were to consider its work done, after reboot the computer can be re-infected. Which means another download of the patch gets started! Can you say "Sorcerer's Apprentice"?

    Even if the worm were smart enough to download a service pack, we're talking over 100 megabytes. That can take a while if you don't have good broadband, and meanwhile it's providing a nice accidental DDoS against microsoft.com.

    --

    --
    "Open source is good." - Steve Jobs
    "Open source is evil." - Microsoft
  106. But your box is already compromised. by Population · · Score: 1

    Unless you want the blaster worm on your box, you've already been compromised.

    I like the idea of having the worm wait for probes from infected boxes and then jumping to them and cleaning them and waiting for more probes.

    Although it would be nice if it tossed up a dialog box saying what it did and how to remove it.

  107. Sigh... this will be modded down again by Anonymous Coward · · Score: 1, Informative

    Every time I have said this on /. it has been modded down as a troll. However, you will find Microsoft now recommending exactly the same thing on their site: http://www.microsoft.com/windowsxp/expertzone/colu mns/northrup/02august12.asp

    If you connect a Windows box directly to the Internet you are asking for trouble. Microsoft's endless list of vulnerabilities, their insane choice of services that they leave open to the Internet, the lameness of Microsoft's update system and the fact that patches only come out AFTER a vulnerability has been exploited insure that you will be compromised at some point.

    All of my Windows machines hide behind a minimalist (less complexity, less holes) Linux firewall and I only ocassionally use IE and never outlook. I have yet to be compromised (crosses fingers, kisses rabbit's foot, continues to install Linux).

  108. Re: So? by AlphaSys · · Score: 2, Insightful

    Well, Joey, we agree on one thing... we both know one admin who will know better next time (we hope) or one position that has a new chance to be filled by someone worthy of pay grade above that of fry-cook. These companies kill me... hiring not only unschooled slobs but lazy ones as well to oversee their most critical infrastructure. It's amazing. It's one thing to run critical services on Windows; it's another to have an unattentive dolt manage them.

    The bad part about it is that these guys bring down the pay grade for more skilled admins both in the Windows and *NIX world.

    --
    Can I bum a sig? I left mine at the office.
  109. 21st century version of CoreWars by DickBreath · · Score: 5, Interesting

    It's the new 21st century version of core wars.

    MS Windows Virus Wars. Comming to a desktop near you. Let the evolution begin.

    --

    I'll see your senator, and I'll raise you two judges.
    1. Re:21st century version of CoreWars by ccp · · Score: 1


      Best Sig. in a long while.

  110. Re:Microsoft by Anonymous Coward · · Score: 0

    "What possible reason is there to have file and printer sharing open to the internet?"

    Microsoft obviously thought that it would be a good idea. All other points are therefore moot. When Microsoft cooks up an "innovation", look out below!!!

  111. Re:Enron? by Anonymous Coward · · Score: 0

    Yeah! Just do like Dubya did with his energy policy! Turn the whole thing over to Enron, just when Enron was dying!!!

    That's the way to fix those "Socialists"!

    P.S.

    In the case of the North American blackout, I don't think that there was a single "Socialist" in sight! There were, however some allegedly crooked capitalists running part of the power grid. Or, are those the "Socialists" that you refer to? They were, after all, wallowing in government subsidies and regulations!

  112. Deja Vu by Theovon · · Score: 1

    Isn't this what happened the LAST time someone wrote an anti-worm?

    Vague recollection here, but someone wrote a worm which was designed to patch a security hole, but that worm caused so much network traffic that networks slowed to a crawl. I think they got into trouble for it too.

  113. utilities connected to the intenet by Anonymous Coward · · Score: 0

    what the hell for?

  114. how come it didn't automatically by wadiwood · · Score: 1

    automatically commence rebooting. That's my least favorite way of getting an 'autopatch'.

    "Too hot" sounds like an automatic message from the motherboard. My intel P4 can do that.

    Sounds like an opportunity for the car radiator CPU cooling system to me.

    --

    -- it must be true, it's on the internet.
  115. Mod parent up?! by GooberToo · · Score: 1

    Someone, please mod the parent up!

  116. Mission Critical? Don't use Windows by Toolsmith · · Score: 2, Interesting
    I find it hard to believe that the mission critical systems at 411, Air Canada, and Ontario Hydro are running Windows. We all know that Windows has major security flaws - why don't the CIOs of these corporations set a mandate to move their mission critical applications over to Solaris, AIX, OS400 or OS390?

    Even if they are using Windows Internet Explorer for the front-end GUI to access the big-iron back-end, at least ensure that they are capable of patching all of their front-office systems. For instance, they should be using enterprise-wide software distribution facilities such as Tivoli Software Distribution.

    If it's not possible to distribute software to the endpoints, at least have a firewall installed in each location, or have firewalls installed in each PC.

    No wonder Air Canada has troubles with bankruptcy - their foundation is not solid. Imagine how much money they lost because of this worm (and last week's power-outage - that's another rant)?

    You will notice a lot of software vendors are now introducing their products into the Linux platform due to corporate demand - many companies want to move away from Windows because of these critical flaws.

    1. Re:Mission Critical? Don't use Windows by acermate433s · · Score: 1

      But then again if they move to Linux they would need to pay royalties to SCO. Damned if you don't, damned if you do

  117. Here come the worms by CowBovNeal · · Score: 1

    When I read the headline "Worm vs. Worm Battle", nanotechnology came to mind. Now instead of people battling each other, worms will do it for us.

    --
    Bush is on fire and its not good for my lungs.
  118. Canadians must be REALLY stupid by Anonymous Coward · · Score: 0

    If they only used the crown jewel of Canadian technology, they wouldn't have this problem. Ironic.

    We'll set aside the fact that it is a copy of a US product and received substantial funding from the US taxpayer.

  119. Worm by Eviscero · · Score: 3, Funny

    I'm going to develop a worm, that mutates into two different worms...one will be the democrats, the other will be the republicans.

    On the first Tuesday in November, one of them will activate and fill your computer, television and radio with loads of bullshit.

    --


    It's not what you know; It's what you can find out.
  120. Fucking zealots! by Robber+Baron · · Score: 0, Flamebait

    What kind of sick airline uses Windows servers to do check in and track flights/passengers. Is their IT department completely slow? They deserve what they get.

    I'll tell you what kind...the kind that NEEDS to run custom apps! The sort of custom apps that can't be or haven't been ported to *nix! You wanna stop beating the "evil Microsoft" dead horse and start offering some USEFUL alternatives, fine. I know I'm going to be waiting a loooong time for that one. Hell, I'm still waiting for a viable replacement for Ms Exchange.

    BTW I support a Medical services provider with numerous Windows boxen in multiple locations (yes, gasp! they run Windows...it's that custom app thing again!) and not one of those boxen succumed to any of the last spate of virii/worms. It's not all that hard to secure Windows. And I know this to be true: If everyone was running *nix, we'd be bitching about the latest *nix exploit!

    Also I can't understand why we don't lay the blame firmly at the feet of who it belongs to, namely the shit-sucking script kiddies that write these things! So a Windows box has security holes in it...so what! Does that give you the right to mess with it? Do you wander through your neighbourhood trying doors to see if any are unlocked? If I leave my door unlocked, do you have the right now to walk in and steal from me? Ethically it's the same thing. These scumbags are not heroes, they're not "Neo" or "Trinity" or "Morpheus", they're little better than the lowest form of common thief and should be treated accordingly.

    --

    You're using her as bait, Master!

    1. Re:Fucking zealots! by Ryokos_boytoy · · Score: 1

      This is hardly flamebait, more like insightful. But given he isn't spouting the psrty line he gets modded down. Thats fucked.

      Let's not blame the victims entirely. If it wasn't for the fucking script kiddies it wouldn't matter that M$ release such insecure trash. And when M$ isn't the #1 OS, we'll see the script kiddies change targets. This reminds me of the looney left blaming guns for murders and not the humans who did the shooting.

      --


      If you don't say anything, you won't be called on to repeat it. -- Calvin Coolidge
  121. Will someone please write a cleanup worm... by scrytch · · Score: 1

    ... that disables sobig.f and all its incarnations? Wondering how small one can make a personal firewall and spread it as a worm. At least a program that monitors for new ports being opened, tests them for being SMTP or SOCKS or whatever else sobig is opening, then pops up a warning saying "your system may be compromised, learn more by clicking here, clean it up by clicking here".

    --
    I've finally had it: until slashdot gets article moderation, I am not coming back.
  122. Good and bad, and a slippery slope by swb · · Score: 2, Interesting

    I see that as a good thing. What possible reason is there to have file and printer sharing open to the internet?

    It's good and bad and something of a slippery slope. When I sign up with an ISP, I want IP service -- the ability to send and receive any and all IP datagrams, regardless of their type or subtype. If my ISP starts filtering my IP service based on the overflowing basket of potential IP-based vulnerabilities, I lose that IP service. That's bad.

    It's also something that "controllers" will want to see implemented based on whatever their agenda is (MSN blocks AIM, RIAA/MPAA wants Kazaa/Gnutella blocked, Ashcroft wants IPSec blocked, et al). That's the slippery slope, and it leads to what amounts to cable-TV internet service -- transparent proxied, web-only service. Yuck.

    The good would be that the ignorant wouldn't be vulnerable, and many of us that manage networks professionally wouldn't have to put up with the amplification effect of millions of infested boxes with terrabytes of bandwidth. Some more obscure worms/viruses would die on the vine, but I highly doubt it will end all of them.

    What ISPs should do is offer a "filtered" internet connection that limits vulnerabilities and charge extra for it. Although I'm sure it'd be a major headache to setup, and potentially a huge liability of the filtering was inadequate to stop a worm or a new vulnerability.

    This would allow for the clueless to get something to help them, and protect people who want real IP service, and not some cable tv-like service.

    Unfortunately, I think the real solution is more, bigger worms: this should shame MS into overhauling their networking security model.

  123. Obligatory Simpsons reference by operagost · · Score: 1
    For decimating our pigeon population, and making Springfield a less oppressive place to while away our worthless lives, I present you with this scented candle.

    Away from the speech, Skinner and Lisa talk.

    Skinner: Well, I was wrong. The lizards are a godsend.
    Lisa: But isn't that a bit short-sighted? What happens when we're overrun by lizards?
    Skinner: No problem. We simply release wave after wave of Chinese needle snakes. They'll wipe out the lizards.
    Lisa: But aren't the snakes even worse?
    Skinner: Yes, but we're prepared for that. We've lined up a fabulous type of gorilla that thrives on snake meat.
    Lisa: But then we're stuck with gorillas!
    Skinner: No, that's the beautiful part. When wintertime rolls around, the gorillas simply freeze to death.

    --

    Gamingmuseum.com: Give your 3D accelerator a rest.
  124. How lame are you? by Royster · · Score: 1

    All it takes is for one home user using VPN or a single laptop user to get infected and then connect to the corporate network to spread it befind the firewall. Blocking port 135 at the firewall is SOP almost everywhere.

    Behind the firewall, port 135 is necessary in Windows networks and can't be blocked without massive breakage.

    --
    I have discovered a truly marvelous sig, unfortunately the sig limit is too small to contain i
  125. No such thing as a beneficial worm by Sun+Tzu · · Score: 1

    A related article sums an argument against beneficial viruses. Unauthorized intrusion is bad, no matter that the perpetrators _claim_ their are good.
    --
    Send us your Linux Sysadmin articles.

  126. disk formatting would be better. by twitter · · Score: 3, Informative
    So the networks are brought to a crawl due to the large amount of traffic necessary to patch systems because incompetent MSCEs are too incompetent to do the job themselves?

    That's a little harsh, don't you think? People did apply patches, they just did not work. The only incompetent thing it to use or recomend Microsoft in the first place. It should be obvious by now that M$ has no place on a network. More than a year after Bill Gates made security job one, M$ still blows and it always will.

    I would have considered a disk formatting worm to be fully justified.

    Well, it would require fewer network services and people could get on with the rebuild job they need anyway. Face it, you can't trust a worm to do your job. If you get either of these, it's time to break out the CDs and rebuild the machine because you can't trust a worm to not be trojaned. That would be nicer than making it so no computer can use a network because these broken boxes are spewing their guts out trying to get M$ patches.

    The answer is to dump Microsoft all together. Free software is obviously superior by now and no one need to spend good money on bad Microsoft software anymore. Disasters like this just go to show the real TCO of that junk. The colatoral damage to people who don't run M$ at all is unaceptable as well.

    You have to wonder if businesses that don't use M$ anymore but were unable to use networks because of it can sue M$ and the dummies that still use them. Sounds like another billion dollar classaction lawsuit followed by thousands of individual suits to chip at the rapidly diminishing M$ pile of ill gotten cash.

    --

    Friends don't help friends install M$ junk.

    1. Re:disk formatting would be better. by PenguiN42 · · Score: 1

      People did apply patches, they just did not work.

      Wait a second here. What smoke are you blowing? The patch works fine. It was out a month before there were any exploits around. It was out, very visibly, in the "critical updates" section of windows update, so even the most braindead users could install it. Machines with the patches installed did not get the worm.

      It should be obvious by now that M$ has no place on a network. More than a year after Bill Gates made security job one, M$ still blows and it always will.

      Why does it blow? Because there are security holes found? Because they release patches for them? Try subscribing to the DEBIAN-SECURITY mailing list and tell me linux never has security holes.

      Sheesh.

      --
      The following sentence is true. The preceding sentence was false.
    2. Re:disk formatting would be better. by KJKHyperion · · Score: 1
      People did apply patches, they just did not work

      Oh, please! find a better excuse. The patch worked perfectly. I wouldn't have the slightest idea of what the shutdown message looks like if, about a year ago, I didn't think "what if I terminate the LSASS process?". Why? because I installed the goddamned patch when I should have, that is more than a month ago, as soon as it came out for my language

      How can people say Windows is not secure? since I upgraded to Windows 2000 from Windows 98, I have never used a personal firewall or an antivirus, and I still have to be infected for the first time (I got a virus only once, on Windows 98, because I double-clicked it by mistake, believing it wasn't a valid executable. Lo and behold, it was Matrix - the last, true virus. After Matrix there have only been these lame web worms). It all depends on how much time you're going to invest initially, and on how much ease of use you can tolerate to sacrifice to security

      Sure, hard-core security is almost impossible to achieve, but mostly because of lack of culture and infrastructure:

      Culture:

      • the NTFS filesystem maker creates a default ACL that allows file execution
      • the ACL editor is very liberal about execution access, always allowing it by default and (in the basic mode) mixing it with the read access, like it was equally harmless
      • Windows Scripting Host should check that the file is executable before executing the scripts within. Similarly, Office should always disable macros for non-executable documents (if execution access wasn't granted by default, this would shield users from the most common worms)

      Infrastructure:

      • to run a service as some specific user, the credentials (username and password) aren't really necessary. You may want to run a service as a lesser user on the local machine, and as an anonymous user on the network (i.e. without credentials, like services running as SYSTEM) - much better security. But Microsoft needs to propagate the lie that Windows is more secure because a password is always necessary (bullshit), so you won't see this in Windows 2003 Server either
      • the management of devices is horrible, compared to the traditional UNIX way. You can't assign names or naming patterns to devices - they either choose their own names or let the system auto-generate them as progressive integers. So there's no reliable way to assign security to devices (e.g. locking out users from the floppy drive). Even the unreliable way requires third-party software, because the Policy Editor rejects device paths like \\.\GLOBALROOT\Device\Floppy0
      • I won't even go into the inadequacies of filesystem mounting. The thing is so broken (and unfixable without breaking existing drivers) that it isn't even funny

      Essentially, it boils down to the fact that Windows 95 was more successful than it deserved to be. The NT team was forced to port the bad joke turned nightmare known as "Win32" to their wonderful system (and they'll probably go to the OS Engineer hell for what they had to do to hide the protected memory nature of Windows NT to Win32), and NT has never been its good, old self, since then (why the hell do we need drive letters in 2003? why isn't the damn CD-ROM mounted by label, so that programs won't complain when you move scratched media from your old, crappy drive to the newer one?)

      --

      Make a difference - use Windows! (open source clone of Windows NT)

  127. Worm vs. Worm? by juaja · · Score: 1

    hmm... T3 anyone?

    --
    I HAVEN'T OWNED A TELEVISION SINCE 1967 AND ONLY WATCH MOVIES ABOUT LEFT-HANDED ALEUT LESBIAN PIPEWELDERS! FUCK HOLLYWOO
  128. Welll well... by fizz · · Score: 1

    Would you look at that! If i remember correctly, in the previous post on /. about lovesan, someone asked about what if someone released a worm to basically FIX msblast, and there were several replies stating how it would make things worse! This proving thier points, that you cant always fix a worm with a worm.

  129. CoreWars by MenTaLguY · · Score: 1

    What this is degenerating into is simply CoreWars on a global scale...

    --

    DNA just wants to be free...
  130. I've got it. by gregarican · · Score: 1
    Here's an idea...taken from a thread I posted to earlier.

    How about state laws dictate that all citizens who purchase a PC provide their PC Operator's License? Similar to a citizen not being able to legally drive without passing a test to obtain a Driver's License.

    It might not be foolproof, but at least it would be a step in the right direction. A PC Operator then would be tested on security patching, software installation and configuration, basic troubleshooting, etc. That might help take care of one third of the problem that exists with worm/virus/exploit damage affecting everyone to the degree it does. Lately an unlicensed driver isn't a big of a threat as a clueless PC owner!

    Then things could be taken a step further and states could require that the other two-thirds of the problem (i.e. - programmers and sysadmins) undergo instructional classes to better prepare and prevent such issues.

    Oh wait, most of these guys did go to some sort of formal training or instructional classes!

  131. Dude, that's embarassinly wrong. by twitter · · Score: 1
    Train wreck? What a total crock from Keynote. here is a well researched article that's easy to read for you. Code Red and other Microsfot transmitted diseases have a destabilizing effect on root DNS, a weakness eveyone without a huge hosts file or cached lookups has. Keynote Systems has been rewareded for such whoring and you should dismiss such a silly statement from them.

    No one is blaming these stupid worms for all their woes. Well, maybe a few airlines can gripe because their ticketing system is completely disabled. The worms are, however, exasperating the blackout's impact, and some have even implicated it as the blackout's root cause. Statements in the New York Times about non fuctioning alarm display sceens being the root cause of the blackout give those rumors weight. In any case, you are missing the point.

    lots of people are (hopefully) going to be scrabbling for WindowsUpdate for patches which will also add to the bandwidth being consumed.

    The God damn worm is consuming bandwith in just that manner. Thanks to Microsoft's brain dead distribution system, that bandwith consumption is nationwide. You can contrast that to free software distribution systems where it's easy to set up a local mirror and theyby reduce the amount of traffic needed by orders of magnitude. I've only got six machines or so, but my bandwith usage is down dramatically thanks to a local mirror. The same benifits can be had, but to a much larger extent, in an organization with hundreds or thousands of machines. Train wreck, yeah, that's about right. One track, all blocked up by broken shit. Hopefully, people are going to be scrambling to replace that M$ junk. How many times do you have to be burnt to learn?

    Statements about lower TCO for M$ junk are equally flawed and embarassing when you factor in the costs of worms like this and weeks of lost business.

    --

    Friends don't help friends install M$ junk.

    1. Re:Dude, that's embarassinly wrong. by skinfitz · · Score: 1

      Train wreck? What a total crock from Keynote. here is a well researched article that's easy to read for you [sciam.com].

      I'm sorry but I cant find anything in there that says the train wreck didnt happen?

      Are you saying that there was not a crash and that there were no cables affected by the crash?

      These stories disagree with you:

      http://www.computerworld.com/industrytopics/energy /story/0,10801,62375,00.html

      http://www.isp-planet.com/technology/2001/baltimor e_bol.html

      http://www.firefighting.com/articles/namFullView.a sp?namID=3365

      ...snip grumble...

      You can contrast that to free software distribution systems where it's easy to set up a local mirror and theyby reduce the amount of traffic needed by orders of magnitude.

      No shit! You know thats really interesting. If only MS had a system like tha... heyyy they DO! In fact you know - I have one. On my network.

      Incidentally in your mirroring system how do you keep all your software up to date and are 100% certain that it hasn't been tampered with?

    2. Re:Dude, that's embarassinly wrong. by Anonymous Coward · · Score: 0

      Wow, you really are a whiny shite, aren't you?

    3. Re:Dude, that's embarassinly wrong. by skinfitz · · Score: 1

      Wow, you really are a whiny shite, aren't you?

      Funny that I was thinking the same thing about you.

      What's the matter? Arguments can't hold water?

  132. Re: So? by Anonymous Coward · · Score: 0
    The people who were damaged by having their network performance degraded by incessant scanning ave been hurt through no fault of their own, but the companies that are vulnerable to damage by worms to the tune of 6 billion dollars were far more irresponsible than the 31337 5(R197 K16613 that released the worm. If you have 6 billion of stockholder's money and you don't take the basic steps to protect it ( like patching your boxen ) then you are acting very irresponsably.

    If you add up the number of people that were hurt by this 'good' worm and compare the trouble saved the people that were successfully cleaned by this worm you might find that this worm actually did a net good.

    There may be people who were aware of the patch and could not apply it for some reason ( maybe the patch broke existing software and they were in the process of fixing the problem when the good worm 'nicely' patched them against their will. That is the main problem I have with this 'good' worm.

    A less obnoxious 'good' worm would have a screen that popped up and explained how the person had become 'infected' and then asked whether the person wanted to be patched before doing so.

    The scanning is a problem too.

    Suppose everyone ran a web server. You could then write a web page that popped up a screen asking if you wanted to install the worm. The worm might include code that replaced the 404 not found error message with the popup notification. Then anyone that got a 404 not found error on your web server would get the worm page and the opportunity to let it spread to them.

    You could have a page that offered to install a 'computer optimizer' with a long EULA that basically gave you rights to do whatever you wanted to their computer.

    If you were mallicious, you could even add a clause that opened the computer to ANYONE that wanted to do ANYTHING to your computer, and watch the chaos ensue when you published the control protocol with a convienent SDK. People would be able to use these legion zombie machines to do any evil thing they dreamt up or even write a worm to delete the hard drives of them all.

  133. Once you go worm... by dfn5 · · Score: 1

    that's what you'll yearn

    --
    -- Thou hast strayed far from the path of the Avatar.
  134. so many trolls in this hole. by twitter · · Score: 0, Troll
    multiple firewalls .. worth nothing if your users dont protect their networks at home.

    Perfect. It's not your fault for recomending and using Microsoft crap, it's your user's fault for not taking precations? No, the root cause of this failure is in Redmond, but your use of their crap is a larger contributing cause to your company's problems than anything any of your users do. Take responsibility for your decisions and fix that mess the right way. How many times are you going to shell out big bucks only to be burnt by the next Microsft Transmitted Disease?

    It is way past time to dump Windows. It's not hard to do, really, and you will be much better off in the long run to start using free software now. Good luck cleaning that mess up. Don't be too hard on the owner of that laptop, there were as many ways for that thing to get on your network as IE has exploits. When you finish restricting your users to things that are "safe" on an M$ network, what exactly will you be providing your users? Free software requires far fewer restrictions while offereing much better services and ease of data trasport. When you factor worms like this and bandwith costs for "patching" into your TCO, free software is a real bargain.

    --

    Friends don't help friends install M$ junk.

  135. typical Microsoft stuff. by twitter · · Score: 1
    Considering the original and first variant of the MSBlaster worm made major headlines, why were these systems still vulnerable? Are each of those systems equipped with a 9-volt battery and a cheap Somebody Else's Problem field?

    From what I read here, M$'s little tools said the machines were "patched" when they were not.

    And don't give me that shit about airline computers having to be 24x7. If that were the case, they wouldn't be running Windows in the first place.

    I won't and they be making that mistake for much longer either. That roaring sound you hear is not a jet engine, it's the sound of millions of IT pros wispering, "I told you so," as they write yet another paper recomending free software everywhere M$ is. M$ TCO is way more than the M$ tax.

    --

    Friends don't help friends install M$ junk.

  136. Windows on bus displays by IncohereD · · Score: 1

    For a while I was regularly seeing the "Welcome to Windows Terminal Server" dialog box on the Ottawa city bus electronic time schedules. They had never even unchecked the "show me on startup box". Tuned that software to the gills, I tell ya.

  137. Too bad... by Junta · · Score: 1

    They didn't name them 'W32.Godzilla' and 'W32.Mothra', that would put things into perspective better..

    --
    XML is like violence. If it doesn't solve the problem, use more.
  138. The pumps run Linux by Anonymous Coward · · Score: 0

    One of serveral possible Point of Sale systems does run NT4 (and had the daylights tested out if it in SQA before release), but the E500 pumps on the island run Linux!

    Also, the POS isn't on the Internet. Updates (and remote troubleshooting) are accomplished by dialing-in. Any card processing networks that might be attached are dedicated and encrypted. The encryption box runs a dedicated OS kernel, not Windows.

    Airlines, utilities, etc., I cannot attest for, but there are no dummies or risk takers where I work. When you handle both financials and flammable liquids, there's no margin for error. Moreover, the flammable side is Linux.

  139. Plagarism alive and well... by RALE007 · · Score: 2, Interesting
    After reading the article, I had a haunting feeling of deja vu, most notably to the paragraph:

    "...Blaster exploited a flaw in most current versions of Microsoft's Windows operating system for personal computers, laptops and server computers. Although Microsoft posted a software patch to fix the flaw on July 16, many users failed to download the patch, leaving them vulnerable to the worm, which first started hitting computers around the world on Monday. ..."

    I could have sworn I had read the exact same statement in a different article a few days ago. The statement had stuck in my head because it implied the worm problem was completely users fault for not installing the patch. Since it seemed so familiar, I googled the phrase "Although Microsoft posted a software patch to fix the flaw" (google limits you to ten words or less). Lo and behold, hundreds of hits for individual separate articles from "different" news sources with the exact same paragraph, completely verbatim. I am aware that information is shared through the associated press, but personally I find it unsettling that all of these news authors do little more than cut and paste another authors words (and voice), instead of writing an article on the same subject with different points of view or ways of expressing the facts. It is especially concerning when the statement in this example seems to slant blame away from a responsible party, Microsoft, in a serious situation that they are largely (IMO) accountable for.

    Perhaps I am off topic, but I felt obliged to point out my discovery. I didn't think it was possible, but my level of trust in the quality of information in the media has dropped yet another rung.

    --
    Beware blue cats moving at .99c
  140. They should have paid attention in kindergarden by Aram+Fingal · · Score: 1

    ...I know an old lady who swallowed a dog.
    She swallowed the dog to catch the cat.
    She swallowed the cat to catch the bird.
    She swallowed the bird to catch the spider.
    She swallowed the spider to catch the fly.
    I don't know why she swallowed the fly.
    Perhaps she'll die.

    Now play nicely.

  141. Remind anyone of CoreWars? by witts · · Score: 2, Insightful

    This worm vs. worm stuff definitely reminds me of watching CoreWars running 2 or more "programs" that are trying to clobber each other. For those not in the know, CoreWars started off in Scientific American Mathematical Recreations article and describes a low-level programming language close to assembly language called Redcode. Using Redcode you write mini programs that are supposed to clobber other programs in Core (aka memory). Fun and fascinating to watch. There are versions for Windows & Linux, so no excuse not to try it. They even have an annual contest, IIRC.

    Maybe it's time for someone to invent Internet-enabled Corewars so that programs can attack each other via broadband...

    --
    pot.kettle(black);
  142. 2 friends so far by Koatdus · · Score: 2, Informative

    So far I have had two friends come over to my house with thier PC's and tell me "It keeps rebooting."

    Both had cable internet. One had no firewall and one had a software firewall. The software firewall had been helpfully turned off by some spyware program. Ad-aware http://www.lavasoft.de found over 200 spyware programs on the pc.)

    I wish someone would release an anti code red worm or two. I still see pages and pages of code red attempts in my logs. After, how many months? , any machine that is not code red patched is probably not going to be.

    While I am ranting how about an anti Kazza worm and an anti Comet Cursor worm.

    I hope no one is working on a worm that changes the passwords in a windows box? That would create a mess.

    Question:

    I am seeing a lot of imcp type 8 traffic and domain-udp traffic aimed at my firewall today from all over the place. Much more then normal. Is the antiworm doing this or something else.

    --
    Every wrong attempt discarded is a step forward - T. Edison
    1. Re:2 friends so far by gregarican · · Score: 1

      The ICMP traffic is the anti-MSBlast worm repeatedly scanning the Internet looking for vulnerable hosts to try to patch. Annoying to say the least.

  143. Jee like this is new!!!! by diverscuba023 · · Score: 1

    oviously someone read Stealing the Network and got the idea from there.

  144. conspiracy theory by Anonymous Coward · · Score: 0
    "...national security is in the hands of Microsoft." - or the other way around perhaps :)?


    NUTBAR CONSPIRACY THEORY


    Yesterday was the 50th anniversary of the U.S. backed coup that overthrew the elected government of Iran and replaced it with a dictatorship. Kind of an embarrassing thing for George II et al to have in the news right now what with Iraq and all. Was it in the news? Course not, between the power failure and the worms and the virus, the news had lots of other stuff to talk about. AND even better, all the commie-mutant-traitors who use the internet to bring up unwelcome topics of conversation couldn't get on-line.

    /NUTBAR CONSPIRACY THEORY


    altho there is some question in my mind as to whether the Committee for Homeland Security is in fact bright enough to come up with this...

    1. Re:conspiracy theory by Anonymous Coward · · Score: 0

      Um, every single day is the anniversary of some US atrocity against the rest of the world. There's no need for nutball conspiracies to suppress public reporting of all that - the media fell in line long ago.

  145. Should be extra for unfiltered. by Steveftoth · · Score: 1

    I disagree, that filtered should be more, rather unfiltered should cost money. Let's face it, the people who want to use the internet as it was designed are in the minority. Most people see it as a service like cable TV. So either you redesign the internet to be like cable TV, or you filter it so that it's safe.

    The internet is cheap because the unwashed masses are useing it. How much money was it to get even a 128k ISDN line to the internet ten years ago? A hell of a lot more then a DSL line is today.

    The internet needs the masses to be a success and I think that it's the duty of the ISPs to ensure that those people don't kill each other with viruses.

    BTW, MS will never be shamed into making secure software, because people don't blame MS for the viruses. Nor should they be. MS is the number one target because it is number one. If Linux, Mac, BSD, Sun, etc. was number one then they would be the number one target.

    1. Re:Should be extra for unfiltered. by swb · · Score: 1

      Filtering should cost more money, since it implies buying the filtering device, time spent maintaining the filter, maintaining the filtering equipment, modifying the filters when a new application everyone wants breaks, lots of technical support, etc.

      Unfiltered IP costs less because there's less work to do.

      If the unwashed are the vast majority, then there's not enough of me to charge more for IP service to pay for the cost of filtering. It makes more sense to charge those who want to be filtered more, since it will be a nominal amount distributed over a larger population.

      MS code is inherently more insecure, and its installed in an inherently more insecure fashion (everything open, all services on, buggy demo code runnable) than most UNIX distributions. Popularity alone doesn't explain it.

    2. Re:Should be extra for unfiltered. by Steveftoth · · Score: 1

      But that's ignoring the costs of what happens because you don't filter.

      The MSBlaster worm shows that the costs of filtering are sometimes lower then the costs of not filtering. The costs of dealing with the Worm are high, it could to have been slowed if ISPs just blocked all inbound connections to normal home users who have no clue. Which is most people. The few people who want to be able to accept inbound connections and run services can pay for the priviledge.

      I know that it's not that simple, and that it's not proven that the costs of filtering are lower then not filtering. In fact, filtering all connections is not only a PITA for ISPs, but goes against the spirit of the internet.

      I do think that the unwashed masses whould rather have a limited connection that works 99% of the time rather then a full connection that breaks their computer. ( and costs them lots of time and $$ to fix )

    3. Re:Should be extra for unfiltered. by swb · · Score: 1

      But the worm/virus costs to ISPs are essentially zero, since it's just a different set of bytes on the wire.

      They're real to ISPs if they infect the ISPs own servers, but that's not a transit cost and ISPs have always had to patch/maintain OSes (and are supposedly better at it, and wouldn't experience the direct costs of the worm themselves.

      They're real costs to *clients* of the ISP, but that's not the ISPs fault, and its an opportunity for the ISPs to sell "security services" (filtered connection, managed firewall, etc).

      Most people would like a filtered connection, but they should have to choose this and have to pay for it, too. :)

    4. Re:Should be extra for unfiltered. by Steveftoth · · Score: 1

      Why do you say that it costs the ISPs no money to have people with viruses on their networks? It costs them money to have bits flowing on their wires, as opposed to not having any bits. I guess if you think that bits are completly free then it makes no difference to them but I'm fairly sure that the cost of everyone using their connection is NOT free to the ISP.

      Also, IMO, selling security services is a bad idea because then the ISP can be held liable when the users DO get viruses, and they will. No amount of filtering will prevent that. However, if they just shut down all incoming connections and don't guarentee that the users will be safe they are out of the loop. Basically, when you're in an untrusted network, (like the internet) paranoia is a way of life. You can't trust anything about a packet that arrives from your incoming interface. And you should always double check your outbound data to make sure it's sane as well.

      ISPs usually pay for how much bandwidth they use, so saving on bits transferred is good for them.

    5. Re:Should be extra for unfiltered. by swb · · Score: 1

      I don't think many ISPs have metered service from their upstreams. Our net connection at work is dual T1, and I've never been offered a metered circuit from our ISP or any other. Considering the next logical step in performance is fractional DS-3, I would have expected our ISP to offer us a "deal" based on metering of a higher bandwidth circuit. Metering is common on colo situations, but that has more to do with the pricing structure of the cage vs. dedicated facilities at the customer location.

      But even if they were metered, the ISPs whose performance data I'm familiar with don't show measurable increases on their upstreams during virus/worm periods. So there isn't a direct cost to ISPs from these things other than customer support blips from the clueless.

      You're right about liabilities, but anything other than a public statement about the filtering of customer connectivity would be a disaster and another potential liability as people who are *expecting* unfiltered connectivity. The only thing for an ISP to do would be to announce they *are* filtering to prevent/stop worms/virii, and that in and of itself would be a potential liability, which is why selling it as a seperate service with a seperate service agreement (with appropriate CYAs for liability) would make some sense.

      Even if you were able to construct an argument as to why filtering would be beneficial to ISPs, you still run into the problem of the management headache and whack-a-mole that filtering presents.

  146. SoBig.F virus also unleashed recently. by Anonymous Coward · · Score: 0

    Noticed an increase in Spam? SoBig.F is to blame, as well as people's stupidity - in that they STILL open unknown attachments.

    Go here: http://www.lurhq.com/sobig.html

    for all the gory details on this little nasty critter.
    Once infected, it's easy to remotely identify an infected host. Details on port usage is listed in the URL above.

    Of course we already now that slashdotters would NEVER open up attachments, right? Right? Please tell me it isn't so.

    Of course it affects WinBlows users, but aren't we ALL winblows users? After all, who wouldn't want to be a Gates slave?

  147. no reason to diss windows by Anonymous Coward · · Score: 0

    The windows OS is being dissed on this server apparently because it is insecure. However, this cannot be the real reason, as follows: Linux, the OS that people most often advocate, has had many, many security problems in the past, equivalent to the windows security problems. Also, just as Linux companies do, Windows released a fix for their problem.

    The main reason that the Windows worm is more dangerous and annoying is because, to use agricultural terminology, there is on the internet a type of Windows monoculture. Because there are so many different variations of Linux in use, it is less likely that an infection could spread, but if a single version Linux was as widely adopted as Windows, it is not hard to conceive of the possibility of an equally damaging worm.

  148. Wait a minute by Anonymous Coward · · Score: 0

    With all the emulated and specialized systems out there, can you guarantee that any code you write will run properly on all systems?

    If the reverse worm only targeted attacking systems, then at least you'd have the guarantee that:

    A) These machines are compatible enough to get infected by the original virus.
    B) These machines are already causing havoc. If left alone, they will continue attacking random hosts until maybe they get discovered by an owner/administrator. You know, unless it's just an old machine sitting in a corner somewhere, or the user doesn't know how to fix the problem, or the admin is on vacation, etc. etc.

    Whoever the idiot is that distributes something like a "clean up worm"...

    One worm r00ts your box and opens up a tftp backdoor. The other worm looks for hosts that are sick or at risk and tries to innoculate them. (Damn those immunization shots, they might get my child sick! Why don't their parents just not let them outdoors?!)

    The cleaner virus is altruistic, performing a benefitial service with the best intentions. The attacker virus is a massive DDOS zombie-maker. It seems to me that the distinction is clear.

    As long as there are exploits, there will be worms. As long as there are automated attack worms, cleaner worms will be beneficial in combatting them. They're a valuable community service.

    Of course, a clever virus writer will take a clue from the root-kit makers: once you own a box, always patch the holes you used to take it over, so some other kiddie can't take it back.

    1. Re:Wait a minute by Shardis · · Score: 1

      "As long as there are automated attack worms, cleaner worms will be beneficial in combatting them. They're a valuable community service."

      I don't mean to come off as a flame here, but I'd have to argue that you don't know what you're talking about. Do some web searching on the current "worm battle", and such virus related events in the past.

      Usually, the clean up worm does as much damage or more damage than the origional. Also, it's a fire and forget system. By definition, it's beyond your control, so a system change later could change how the worm/virus affects the computer. This HAS happened before:

      (credit to Satan's Librarian for this tidbit)
      The 'original' virus that cleaned up another one was the DenZuk virus, which cleaned up Brain. Both virus profiles are available at datafellows. This is like late 80's stuff. DenZuk started corrupting floppies when the new high density ones came out.

      Anyway, I've never met one professional and competant programmer that would be willing to write a "beneficial" worm like this and that would be willing to publically take credit. And I've met a lot of dev's. That alone ought to tell you something...

  149. Thank you! by tres · · Score: 1

    Excellent information, thank you very much.

    One of those golden moments of Slashdot.

    --
    Notes From Under *nix: blas.phemo.us
  150. A new name for a new class of worms by Schol-R-LEA · · Score: 1

    Might I suggest that this be named the Morgaine worm? ;-)

    Or perhaps the class of worms could be called 'Changeling' worms, with individual ones given names like Ivrel, Shiuan, etc.

  151. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  152. Re:So? by Anonymous Coward · · Score: 0

    Even if it WERE true the power outage was the effect of the MSBlaster worm, do you think that M$ is going to allow the press to have a field day? Come on you guys, ol Billy boy controls the media.... and you can best bet your sweet dippy that ol Billy boy is NOT going to want this kind of publicity.

  153. All the fault of idiots by Anonymous Coward · · Score: 0

    I have dozens of windows boxes running and I have NEVER been virus infected. Why? Because I'm not a fucking idiot. I recommend that people too stupid to run a firewall and antivirus software switch to Linux or Mac, OSes so marginal that nobody bothers to write virii for them

  154. Correction by Schol-R-LEA · · Score: 1

    That should have read "renamed the Morgaine worm." Sorry, I'm surprised I didn't catch that in preview.

  155. Be sure to send those crash photos to these guys.. by usrerco · · Score: 1
    Send those windows crash photos to these folks.. they collect 'in the field' screenshots:

    http://www.windowscrash.com/

    ..they have everything from ATMs to giant billboards and massive two story LED signs on the sides of buildings.

  156. simple facts. by twitter · · Score: 1
    Wait a second here. What smoke are you blowing? The patch works fine. It was out a month before there were any exploits around. It was out, very visibly, in the "critical updates" section of windows update, so even the most braindead users could install it.

    Not true. Competent system administrators are saying that the update utility downloaded the patch but did not install it, yet reported it installed. Some help that is.

    Why does it [Microsoft software] blow?

    Development model, marketing model, distributio model, design problems and bad attitude and ethical problems. Where do you want me to start? The results are in, every few months when an new exploit costs everyone lots of grief. Try subscribing to the DEBIAN-SECURITY mailing list and tell me linux never has security holes.

    I've got http://security.debian.org in my /etc/apt/sources.list file and it works great. Free software is like that. You need to look at the uptime lists on netcraft before you mouth off about the security and stabilty of free software as opposed to MicroShit.

    --

    Friends don't help friends install M$ junk.

    1. Re:simple facts. by PenguiN42 · · Score: 1

      Competent system administrators are saying that the update utility downloaded the patch but did not install it, yet reported it installed.

      That's a problem with the update utility, not the patch. You said the patch didn't work. The patch works fine.

      And IIRC it was only a problem when your registry had exceeded its quota. No competent system administrator would allow that. It's like having your /var/tmp partition be full and complaining when apps don't work right.

      I've got http://security.debian.org in my /etc/apt/sources.list file and it works great.

      I know, works great for me too.

      But you were talking about the security holes in the software, not the competence of the patching system. My point was linux has just as many security problems as windows.

      before you mouth off

      I wasn't mouthing off. I was countering exactly what you wrote, as you wrote it.

      Your point about uptimes is well taken, however. I really do appreciate the fact that apt-get update almost never requires a reboot, where every little microsoft patch almost always does. (Kernel security patches do require reboots though!)

      --
      The following sentence is true. The preceding sentence was false.
  157. Re:I predict that we haven't seen the last of this by DotWarner · · Score: 1
    Just as I posted in the first thread about Welchia:
    The Cheese worm did this on compromised Linux systems a few years back. The antivirus industry, in accordance with Linux sysadmins everywhere, added detection for the worm. A virus is a virus, and any unauthorized access to a computer is a Bad Thing.
    It amazes me how many people in that thread regarded this as a clever, useful thing to do, while in this one it is universally declared an obvious problem.
  158. Worm Vs. Tron by Icephreak1 · · Score: 1

    Screw you, worm. You're fucking up my Tron 2.0 ping.

    - IP

  159. Obligatory Simpsons Quote by iMMo · · Score: 1

    Skinner: Well, I was wrong. The lizards are a godsend.

    Lisa: But isn't that a bit short-sighted? What happens when we're overrun by lizards?

    Skinner: No problem. We simply release wave after wave of Chinese needle snakes. They'll wipe out the lizards.

    Lisa: But aren't the snakes even worse?

    Skinner: Yes, but we're prepared for that. We've lined up a fabulous type of gorilla that thrives on snake meat.

    Lisa: But then we're stuck with gorillas!

    Skinner: No, that's the beautiful part. When wintertime rolls around, the gorillas simply freeze to death.

  160. Too bad Microsoft can't be held responsible by syschuck · · Score: 1

    Ever read the EULA?

  161. You're probably right. by danielsfca2 · · Score: 1

    I agree that it would be fraught with problems, and I, as a poor programmer, wouldn't attempt it.

    While any problems caused by installation of MS patches aren't really the fault of the writer of the worm, they are another reason why I'm glad my idea is only theoretical.

    You are right, I admit, that it would be virtually impossible to create a "white hat" worm that didn't screw up approximately as much as it would fix.

  162. ?? about other aspects by stopntalk · · Score: 1

    Another question on same vein. I've been getting about 20 hits per hour since 8/14 that resolves to my ISP's DNS server. Is this an indication they are infected with the anti-worm as well? They don't, as expected have a clue, saying their systems are patched, no abnormal traffic across the system. I asked them to check their outgoing traffic on the server to see if they have an inordinate amount of traffic. No answer. And I still keep getting hammered by my ISP's server. Don't know how long software firewall is going to keep everything out at the rate it's being hit.

  163. sick airline uses Windows servers by SgtChaireBourne · · Score: 1
    I agree. In these financially tight times, it seems that they could be spending the money more effectively. In the last few months, I've seen both bus schedule kiosks and even schedule in the airport hanged with obviously fatal MS-Windows errors.

    Especially for airports, it's not a good idea to put something as half-baked as MS-Windows in services that passengers depend on -- it makes you wonder how good the rest of their work is, e.g. safety, security, and maintenance.

    With the bus schedules, it's just an inconvenience and mildly aggrevating, but nothing a paper schedule or a ride in a taxi won't solve. Though it is wasted money that could be used more effectively in other activities.

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
  164. Canada by icewitch · · Score: 1

    Given that the USA hates Canada for being liberal towelhead-loving bastards for not joining in the glorious liberating (omigod-noone-told-us-our-boys-would-get-killed-an d-we-should-have-left-it-to-the-United-Nations-lik e-everyone-told-us) war against Saddam, is it only me that's not surprised it's Canadian networks that are affected by the patching worm?

    --
    bored and underpaid
  165. Require license to use computer/internet! by Anonymous Coward · · Score: 0

    I believe the ultimate solution to this problem is to forbid incompetent people from using a computer or accessing the Internet. Do we allow random people to drive cars? No, they have to get a license first. Do we allow kids to drink alcohol? No, they have to be of legal age first (aka, have an ID card). Do we allow random citizens to practice medicine or law? No, they have to go to school and get a license first.

    So why should it be any different with computers?

  166. OSJ by Anonymous Coward · · Score: 0

    I, for one, welcome out new worm overlords.

  167. our by Anonymous Coward · · Score: 0

    D'oh!