Cable Forum - View Single Post

DeadKenny · 23-10-2003, 20:09

The only concern I've got is not NTL blocking a specific port, but once they start with one port, they could start blocking others. I'd rather NTL retained their "no blocking" policy (though I'd also like it if they stopped using transparent web proxies... or at least fix them).

As for port 135, well okay, there are ways around it and if it's only used for Exchange then just use VPN. Any corporate with any sense wouldn't open it to the outside world without tunnelling using VPN or SSH anyway.

VPN is "allowed" on NTL... or at least it's not disallowed. It's just not supported. All the AUP says is that NTL reserve the right to stop you using it if it causes network problems. I'm not aware that VPN could cause them problems (no where near as many as all these worms and P2P software).

Blocking port 135 is a short term solution as the hackers move on to other ports.

I don't think NTL should do anything and just leave it up to the users to get firewalls and Microsoft to patch things up and educate their users. If NTL really want to do something, maybe they should buy firewalls for their customers (Barclays did that for a while).

Unix is not invulnerable either. There's a flaw (one of many) in many linux router kernels open to ICMP attacks. Being routers they're often forgotten about.

The real solution to all this is to prosecute the hackers.

23-10-2003, 20:09	#57
DeadKenny Inactive Join Date: Jul 2003 Location: Woking Age: 53 Services: PlusNet 2Mbps Premier. BT. Sky Digital. TiVo. Posts: 273	Re: NTL to block port 135 The only concern I've got is not NTL blocking a specific port, but once they start with one port, they could start blocking others. I'd rather NTL retained their "no blocking" policy (though I'd also like it if they stopped using transparent web proxies... or at least fix them). As for port 135, well okay, there are ways around it and if it's only used for Exchange then just use VPN. Any corporate with any sense wouldn't open it to the outside world without tunnelling using VPN or SSH anyway. VPN is "allowed" on NTL... or at least it's not disallowed. It's just not supported. All the AUP says is that NTL reserve the right to stop you using it if it causes network problems. I'm not aware that VPN could cause them problems (no where near as many as all these worms and P2P software). Blocking port 135 is a short term solution as the hackers move on to other ports. I don't think NTL should do anything and just leave it up to the users to get firewalls and Microsoft to patch things up and educate their users. If NTL really want to do something, maybe they should buy firewalls for their customers (Barclays did that for a while). Unix is not invulnerable either. There's a flaw (one of many) in many linux router kernels open to ICMP attacks. Being routers they're often forgotten about. The real solution to all this is to prosecute the hackers.