[80750] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Blocking port udp/tcp 1433/1434

daemon@ATHENA.MIT.EDU (Joe Maimon)
Wed May 11 15:19:55 2005

Date: Wed, 11 May 2005 15:16:45 -0400
From: Joe Maimon <jmaimon@ttec.com>
To: nanog@nanog.org
In-Reply-To: <428229F3.5030904@ttec.com>
Errors-To: owner-nanog@merit.edu




Joe Maimon wrote:
> 
> Is there still justification for denying transit for ms-sql slammer ports?
> 
> 
> Thanks,
> 
> Joe
> 
> 

Thanks all for your responses. To me it appears that

a) If you block 135/445 you should block slammer as well
b) If the number of potential infected hosts connected to your network 
can threaten your service, you should block.
c) If you are more concerned about eliminating crap on the net than in 
accomodating every whim of your users and are not doing pure transit, 
block it.
d) Microsoft should consider migrating to a new port for sql server.
e) if you are doing pure transit and not blocking anything, nobody will 
expect you to block slammer either.
f) slammers half life is incredibly long

Does anybody have any idea of the rate of NEW slammer infections?

Thanks,
Joe

home help back first fref pref prev next nref lref last post