-- Jeremy Howard <[EMAIL PROTECTED]> on 09/19/01 06:37:15 +1000 >> This one's gonna grind the net to a halt pretty quick. I hate to think > what >> this will mean for people running web servers at home over DSL (including > me >> soon). >> > Any suggestions on how we should respond? Update Apache::CodeRed to > recognise the new signature, and send an appropriate message to postmaster > and webmaster with an updated URL to point to? Tickle your external filtering router and drop all packets to port 80. You won't get anything done until this thing dies anyway, and especially home systems can usually afford a few hours of downtime w/o the sky (or aggravated users) falling around you. sl
- RE: [OT] New Micro$oft vulnerability? Matt Sergeant
- Re: [OT] New Micro$oft vulnerability? Adi Fairbank
- Re: [OT] New Micro$oft vulnerability? Tom Servo
- Re: [OT] New Micro$oft vulnerability? Nathan Torkington
- Re: New Micro$oft vulnerability? Mithun Bhattacharya
- Re: New Micro$oft vulnerability? Michael
- Re: [OT] New Micro$oft vulnerability? Angel R. Rivera
- Re: [OT] New Micro$oft vulnerability? Nathan Torkington
- RE: [OT] New Micro$oft vulnerability? Alex Porras
- Re: [OT] New Micro$oft vulnerability? Jeremy Howard
- Re: [OT] New Micro$oft vulnerability? lembark
- Re: [OT] New Micro$oft vulnerability? Reuven M. Lerner
- Re: [OT] New Micro$oft vulnerability? Nathan Torkington
- Re: [OT] New Micro$oft vulnerability? Larry Leszczynski
- RE: [OT] New Micro$oft vulnerability? Geoffrey Young
- RE: [OT] New Micro$oft vulnerability? Geoffrey Young
- RE: [OT] New Micro$oft vulnerability? Lyle Brooks
- RE: [OT] New Micro$oft vulnerability? Nick Tonkin
- RE: [OT] New Micro$oft vulnerability? Geoffrey Young
- Re: [OT] New Micro$oft vulnerability? Tim Peoples
- Re: [OT] New Micro$oft vulnerability? Tim Peoples