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