View Single Post
Old 16-10-2003, 21:03   #32
Shaun
Inactive
 
Join Date: Jun 2003
Posts: 6,064
Shaun has a nice shiny starShaun has a nice shiny star
Shaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny star
Re: NTL to block port 135

Quote:
Originally Posted by BBKing
Exchange is a very small part of what 135 is used for - the significance for ntl (and other ISPs, and all internet users) is that it:

1) is left open by default on MS Windows installs
2) connects to parts of Windows that are prone to very serious bugs that can lead to machines being taken over.

This has led to it being used as a method of infecting Windows machines with viruses which cause degradation to service on the internet, which naturally ntl isn't too happy with (as it puts up the call rate and makes the customers very unhappy, and, contrary to public opinion, we like happy customers). So blocking it off *should*:

1) reduce the number of new infections, as your nice shiny new Windows install won't instantly get infected
2) reduce the number of hits on people's firewalls
3) give us some breathing space to get round to disinfecting everyone who's infected.
So when I suggested it and was shot down with people saying that it was a really stupid idea, I was in fact right.

If this is so why on earth was it not implemented earlier???
Shaun is offline   Reply With Quote