Slashdot Mirror


Code Red: the Aftermath

LiquidPC writes: "Microsoft has released a tool to help clean up the effects of the Code Red II. It removes the files and mappings installed by the worm, and reboots your system; it also gives you an option to permanantly disable IIS." So, Microsoft has given you a mop to clean up the mess they made. Start mopping! If you're not the one infected, just tired of seeing your Apache logs fill up, you might see this page.

6 of 505 comments (clear)

  1. Re:No. by spectecjr · · Score: 1, Flamebait

    Umm... WRONG!

    You won't be able to "put a stop to this this thing really fast" no matter what you do. M$/IIS is bloatware chocked full of undiscovered exploits. This is not the last of THIS TYPE of worm.

    AND! yes it does say something about the character of the IIS admins, because it takes very little technical know how to get a IIS server running. ("I had IIS running? I had no idea") Like I said! Uninformed, ignorant, or lazy! PICK ONE!

    I for one am glad. This is just the type of thing that can actually cause enough damage to the already tarnished track record of M$ commercial server market, to help see a real decline in there numbers.

    IIS is a disease. Apache is the cure.


    Dumbass, IIS wasn't exploited by Code Red. Index Server was.

    If you were running APACHE and had it bound to Index Server (not that farfetched on Win2k), you'd STILL have had a rooted box.

    Simon

    --
    Coming soon - pyrogyra
  2. Re:About time! by SuiteSisterMary · · Score: 1, Flamebait

    Are you stupid? The first rule of system hardening is 'turn off services you don't need.' Pretty much every network operating system (except, I believe, certain variants of *BSD) tends to run daemons which generally aren't necessary. And I'll note that Bastille Linux turns off unneeded daemons as part of it's hardening routine.

    --
    Vintage computer games and RPG books available. Email me if you're interested.
  3. Re:Stop blaming microsoft by Crixus · · Score: 3, Flamebait
    I agree with you not to blame MICROS~1. Blaming them is like blaming a glass manufacturer for when a robber breaks a window, and steals your tv. Blame the damn virus writer! And blaming the sys admins is like blaming the owner of the house because he/she does not know that the glass they bought with the house is NOT bullet proof.

    No, no, no.

    When you buy a house, you know for a FACT that glass will break when hit with a hammer.

    The people who buy MS products THINK they're getting something secure, since it's one of the many buzzwords (READ: lies) that MS always uses.

    Your analogy just doesn't do justice to the situation.

    Rich...

    --
    Ignore Alien Orders
  4. Re:Not the mess they made... by ZxCv · · Score: 0, Flamebait

    This deserves a -1,Retard.

    I've been using different variants of UNIX for about 10 years and Windows for about 8. And as a competent professional, I know how completely absurd it is to assume that because someone is using Windows, they have no computer savvy.

    Think a little bit before you post next time...

    --

    Perl - $Just @when->$you ${thought} s/yn/tax/ &couldn\'t %get $worse;
  5. Re:No. by rambot · · Score: 0, Flamebait

    are you going to criticize stupid shit, or are you going to talk about the issue at hand ya fuckin flame bait bitch.

  6. Re:Anybody who thinks... by Anonymous Coward · · Score: 0, Flamebait

    Oh no. 132 probes in a 24 hour period from dial ups!

    Sounds like a big immergency!

    I'm suprised you can even get online to post this!