Cable Forum

Cable Forum (https://www.cableforum.uk/board/index.php)
-   Virgin Media News Discussion (https://www.cableforum.uk/board/forumdisplay.php?f=10)
-   -   More port blocking (https://www.cableforum.uk/board/showthread.php?t=4037)

preacher 06-11-2003 14:41

Re: More port blocking
 
Quote:

Originally Posted by philip.j.fry
I should hope I'm educated by now, if not I'll be in trouble when I reach my finals at the end of the semester :spin:

:LOL: Good luck with them matey! :Peace:

albone 07-11-2003 19:52

Re: More port blocking
 
I personally think the best way to aproach this problem, is for NTL to place a virus protector on their side, so that all downloads are virus free! That way if a virus is detected, it would get bashed on the head before the unsuspecting public get the hassles. Surely that would be far easier than blocking ports and having to try and educate some of the 'know it all's' there are around, who think they are not ever likely to be infected and refuse point blank to have any virus/firewall on their computer. A lot of computer suppliers are now making sure they are sold with it anyway.(if they are reputable that is.)

Maggy 07-11-2003 20:53

Re: More port blocking
 
Quote:

Originally Posted by albone
I personally think the best way to aproach this problem, is for NTL to place a virus protector on their side, so that all downloads are virus free! That way if a virus is detected, it would get bashed on the head before the unsuspecting public get the hassles. Surely that would be far easier than blocking ports and having to try and educate some of the 'know it all's' there are around, who think they are not ever likely to be infected and refuse point blank to have any virus/firewall on their computer. A lot of computer suppliers are now making sure they are sold with it anyway.(if they are reputable that is.)

would this be financially viable?because i suspect it would just put up costs.as a customer who has got av and a firewall that i have paid for i don't see why costs should go up because there are those that won't listen to reason.

incog. :kiss:

Alan Waddington 07-11-2003 21:21

Re: More port blocking
 
I don't have a major problem with blocking the microsoft networking related ports (135, 137, 445 etc.) but question blocking ports above 1024. I don't think many home users run MS SQL, so why is this considered a risk. The other port mentioned in NTLs news item appears to relate to a port used by trojan software. Since trojans can be written to use any port, surely this approach will result in an increasing level of denial of service to customers as more ports are blocked.

Alan :(

Stalker 08-11-2003 13:36

Re: More port blocking
 
I do have a problem with these ports being blocked, some games run on ports above 1024, does this mean that i won't be able to have a game of good ol Delta Force????

NTL dont seem to get it trough their heads :knock:

§talk

Paul 08-11-2003 13:37

Re: More port blocking
 
That particular trojan (Sub seven) is quite old now and I think newer versions of it use different ports.
I see very few instances of that port turning up in my firewall logs now (on my non NTL servers).

fraz 08-11-2003 19:17

Re: More port blocking
 
Quote:

Originally Posted by pem
Q. When is an ISP not an ISP ?

A. When it's NTL.

I pay for access to the Internet - all of it - not the parts that NTL think I need. Can I expect a reduction in price now I have a reduction in service ?

I hardly call a reduction on the amount of network cruft in my firewall logs from other customers who are too damned lazy to install antivirus progs/keep their OS uptodate a reduction in service.

Exactly what reduction in service have you noticed ?

Chris 08-11-2003 20:24

Re: More port blocking
 
Quote:

Originally Posted by fraz
I hardly call a reduction on the amount of network cruft in my firewall logs from other customers who are too damned lazy to install antivirus progs/keep their OS uptodate a reduction in service.

Exactly what reduction in service have you noticed ?

The number of available ports has been reduced, ergo, the available service has been reduced. To ask whethe anyone has 'noticed' is to obscure the issue. The service has been reduced, whether I am aware of it or not.

But, for what it's worth, I will notice it when, due to NTL blocking ports above 1024, I get the occasional "page not found" error. And if I ever sign up for distance learning and expect to connect to the university systems using any of the methods now disbarred by NTL (note, this is still a legitimate residential use), I would sure as eggs is eggs notice it.

Even NTL has acknowledged that some customers will be affected, fraz, you really don't have to try to fight the battle for them.

fraz 08-11-2003 20:41

Re: More port blocking
 
Quote:

Originally Posted by towny
The number of available ports has been reduced, ergo, the available service has been reduced. To ask whethe anyone has 'noticed' is to obscure the issue. The service has been reduced, whether I am aware of it or not.

But, for what it's worth, I will notice it when, due to NTL blocking ports above 1024, I get the occasional "page not found" error. And if I ever sign up for distance learning and expect to connect to the university systems using any of the methods now disbarred by NTL (note, this is still a legitimate residential use), I would sure as eggs is eggs notice it.

Even NTL has acknowledged that some customers will be affected, fraz, you really don't have to try to fight the battle for them.

Can I just point out that if you trawl back through the last 5/6 years worth of my online activities I've never been a particualrly big fan of Net Nanny ISPs however quick reality check:

The number of internet users now online that simply buy their PC and expect to use it in the same manner as they use a Microwave (or any other item of white goods) now far exceeds the number of enthusiasts using the net. ISPs (& I'm not singling out NTL) are changing the way that they provide a product to their customers and Blaster/Welchia gave all ISPs a short sharp shock.

Alan Waddington 08-11-2003 21:32

Re: More port blocking
 
Quote:

Originally Posted by fraz
ISPs (& I'm not singling out NTL) are changing the way that they provide a product to their customers and Blaster/Welchia gave all ISPs a short sharp shock.

I agree there is a problem & that blocking the microsoft networking ports will block a popular route of infection. I feel this is a reasonable compromise.

On the other hand blocking ports above 1024 is only effective as a short term solution as virus writers are likely to write future trojans to use ports that aren't blocked by major ISP. Hence this becomes an arms race, with more & more ports becoming blocked.

I an wondering what happens when I buy software over the internet, which allows only 2 or 3 download attempts. Normal FTP could fail & if a second attempt also gets a blocked port, it is possible that it could be difficult to recover the situation. I am unsure how ports are allocated, but if it is based on cyclicly searching for the next free port starting from the last allocated port, then blocking port ranges could be a problem. Anyone know if this is actually likely to happen.

Lastly, it occurs to me that it would be possible to write a trojan that hops ports on a time basis (just like frequency hopping on older secure radio links). Provided the time between hops is fairly long and the victim's PC's clock is set correctly, then the virus writer would have no difficulty determining the open port at any time. And what about the approaches taken by peer-to-peer networking software. I don't know how those work, but I have heard that port blocking is ineffective on those due to non-fixed port usage. So I say again, port blocking above 1024 is an unwinable approach and can at best be considered a temporary measure.

To end on a more pleasant note, I would like to reiterate that blocking 135, 137, 139 & 445 seems a good idea to me. Well done NTL.

Alan :banghead:

homealone 08-11-2003 22:23

Re: More port blocking
 
Quote:

Originally Posted by Alan Waddington
To end on a more pleasant note, I would like to reiterate that blocking 135, 137, 139 & 445 seems a good idea to me. Well done NTL.

absolutely - but it isn't "the end" of those exploits, I had a look at my router log, just now and still got a 445 probe two minutes ago. - local of course, but people should still beware - imo.

piqueaboo 09-11-2003 01:24

Re: More port blocking
 
Quote:

Originally Posted by Alan Waddington
I don't have a major problem with blocking the microsoft networking related ports (135, 137, 445 etc.) but question blocking ports above 1024. I don't think many home users run MS SQL, so why is this considered a risk.

Exactly.

I expect the real problem the sql & subseven ports this solve is the number of Mr Angry e-mails abuse get about PFW entries. That NTL are prepared to randomly break customer applications for that is appalling.

If they really must block these ports why couldn't or wouldn't NTL use stateful filtering i.e. just stop inbound SYNs?

Router performance? I hope so because at least that implies a limit to how much they can break.

Paul 09-11-2003 14:08

Re: More port blocking
 
Quote:

Originally Posted by fraz
Exactly what reduction in service have you noticed ?

If they block ALL 139, 445 then I will lose the ability to connect to my remote computer shares, that is a big loss of service to me.

fraz 09-11-2003 17:08

Re: More port blocking
 
Quote:

Originally Posted by pem
If they block ALL 139, 445 then I will lose the ability to connect to my remote computer shares, that is a big loss of service to me.

Not being funny but how many people 'knowingly' use Windows File & Printer Sharing over a public network (your internal network wont be affected by the blocking) especially when there are more secure alternatives such as FTP or SCP for transferring files etc across the internet.

Chris 09-11-2003 18:05

Re: More port blocking
 
Quote:

Originally Posted by fraz
Not being funny but how many people 'knowingly' use Windows File & Printer Sharing over a public network (your internal network wont be affected by the blocking) especially when there are more secure alternatives such as FTP or SCP for transferring files etc across the internet.

I expect there are only a few people affected, as NTL's FAQs say, but now you are shifting the debate away from the point you tried (unsuccessfully as it happens) to make earlier.

Originally you asked, 'have you even noticed?' Pem's answer to that is clearly 'yes'. You can't just go changing the question when your original point proves wobbly.


All times are GMT. The time now is 15:56.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum