North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
RE: Providers removing blocks on port 135?
Well, we could start by having every ISP do what we do, which is to find worm-infected customers inside our network and get them patched or turned off. But that's a lot of work. (Especially when you've got a new worm to track down every week) The scary/unfortunate part to me is that these things never seem to go away... Check your web server's log for the last hit from Code Red, for instance. (6 minutes ago, from 188.8.131.52, on the server I just checked) Matthew Kaufman firstname.lastname@example.org > -----Original Message----- > From: Owen DeLong [mailto:email@example.com] > Sent: Friday, September 19, 2003 10:23 AM > To: Matthew Kaufman; 'Jack Bates'; 'Adam Hall' > Cc: firstname.lastname@example.org > Subject: RE: Providers removing blocks on port 135? > > > OK... Obviously, you need to do what you need to do to keep things > running. However, that should be a temporary crisis > response. If your > equipment is getting DOS'd for more than a few months, we need to find > a way to fix a bigger problem. Permanently breaking some service > (regardless > of what we think of it. Personally, I'll be glad to see M$ > go down in > flames) > is _NOT_ the correct answer. > > Owen >